This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
Reproduction:
Create a Silverlight project
Turn it to version 5
Add references to the Silverlight Toolkit (using NuGet or direct)
Add a DataForm to your page
This is the exception the DataForm constructor throws:
{System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows.Controls.Data.Input, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
[IO.FileName_Name]
Arguments: System.Windows.Controls.Data.Input, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.0.60401.00&File=mscorlib.dll&Key=IO.FileName_Name
at System.Windows.Controls.DataForm..ctor()}
Turn back to Silverlight 4
Now everything is cool again
Weird note: it does work in the VS/Exp. Blend 5 designers
Any ideas?? Workaround???
Found a very strange workaround: After I returned the SL version to 4, and re-returned it to 5, everything works! (?!?)
Anyway I'm sure recompiling the source-code of the SL TK targeting SL5 will help anyway.
I could not resolve this problem, also taking a project that was SL version 4 then migrating to SL version 5 and trying to add a DataForm. Even though I referenced the December 2011 Silverlight 5 Toolkit, and I added a proper reference to the SL5 DataForm, because of the presence of SL version 4 assemblies I get an error.
Not sure how you can 're-return' and 'return' as suggested in the workaround but for now I think anybody migrating from SL 4 to SL5 and trying to add a dataform will experience this problem. Best to either start from a completely new SL5 project, or, forget about using dataform with a SL4 solution migrated to SL5?
Related
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 10 years ago.
I created a brand new MVC4 app. Installed new signalR package from NuGet:
Install-Package Microsoft.AspNet.SignalR –pre
Whenever I run it, it loads indefinitely. I know it is caused by SignalR => App_Start/RegisterHubs that was added during install because it never gets passed "RouteTable.Routes.MapHubs(); " line when in debug.
tried it on several machines running windows 7 and Vs2012 and IIS Express
what gives??
thanks
UPDATE:
I just tried it on my home computer. Created a brand new MVC4 app, ran nuget package install and IT WORKS FINE! :) (same set up vs2012, win7, IIS express).
This is weird because everything AT MY OFFICE worked just fine until i installed the new version of signalR.
could it be that at work we're behind a proxy?
-why would that make a difference?
-how can I check if all the files are installed correctly during nuget install at work? What should should i be looking for/check?
one more thing: When I had previous/older version of signalR installed (without the RegisterHubs file) everything worked fine.
thanks
And, For indefinite load times when running the site on IIS Express, Please check your IIS from ControlPanel-->Programs and Features-->Turn windows features on or off-->Internet Information Service. Check whether all the relevant features are assigned in World wide Web services under IIS., I came across with Same issue., I activated relevant features., Now, No indefinite loading.., :) Hope it will helpful for you or someone.
thanks,
Shanthini.
Found the solution:
Changing from IIS Express to VS Development Server OR Local IIS helped. Now everything works fine. Not sure what caused indefinite load times when running the site on IIS Express with Proxy at work.
thanks
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
Every page we publish increases around 2 MB memory on server. Is it a configuration issue?
FYI it is SDL Tridion 2011 SP1 with old vbscript code.
Please sugegst.
No - it is not a configuration issue.
At least, that is, assuming that what you are seeing is a memory leak. Tridion does cache various items during rendering, and some of that cache behaviour is configurable. Are you saying that the memory increases with every page render? And that it doesn't come down again? Which process owns this memory? Is it the publisher service, or the COM+ surrogate (dllhost), or something else?
It is impossible to cause a memory leak simply by configuring Tridion.
Are there any errors showing up in your event logs that might shed some light on this? Don't forget to look in the Application/System logs as well as the Tridion logs.
Does it increase all the way until it stops responding? Or is this memory re-claimed later?
Using VBScript templates is not necessarily an issue, but I would certainly try to ensure that all your objects are released properly in the templates (set them to Nothing) and a code review is always a good idea.
As Dave suggests, testing with the Default Templates is always a good idea.
I think the most important comments have been made. This is most likely a memory leak caused by not releasing objects where you have used Set blah = foo and not using Set blah = Nothing to release it. But if the Publisher does not keep growing to the point of failure, it could just be good caching of your templates by the publisher.
For earlier releases of Tridion, we had a community built PowerTool (available on the BBX of SDLTridionWorld.com) called CodePlumber which looked for such leaks. As you clearly know VBScript (and the tool is written with VbScript based classic ASP) it may be worth reading that code or resurrecting it to test your templates. You may even want to earn some bonus points for migrating it to the new PowerTools for 2011 framework.
My final question is whether or not these templates have been moved from an earlier version of Tridion, and if so whether the same memory growth was observed. If not, you may be seeing a new issue with how legacy templates are handled in the publishing process.
You don't mention where the memory is increasing, but the most common place is in the COM+ object.
If this is the case, the brute-force method of working around this is to implement COM+ recycling at a memory threshold. The threshold would depend on where you start to see issues, and the available memory on the server, but 1GB is a good point to start tuning from.
This recycling should have no impact on your user's experience.
Note this doesn't actually fix the issue - it simply prevents the issue from bringing down the rest of the system.
As the other posters have mentioned, fixing the issue likely means tracking down memory leaks in your old VBScript code.
I know there are several questions asking the same question "Why should I use release mode". The problem I have with the answers is that they simply state, quite strongly, that you should always use release mode when a website is in production.
Why?
I understand that the code is optimised in the assemblies, but to what level? Is it going to optimise well written code? What kind of optimisations does it perform?
Are there any analyses regarding this? Is there anyway I can test the differences between debug and release?
I would really like someone who understands the why of this to at least provide a reference to some definitive reading material, as I have yet to find anything hard enough to satisfy my curiosity on this issue.
Read this first: http://blogs.msdn.com/tess/archive/2006/04/13/575364.aspx, I just found it as part of answering this question, its a great article.
See this question: At what level C# compiler or JIT optimize the application code? for some info on general compiler optimizations.
Also, keep in mind that for a Asp.Net web application changing to release mode will compile the assemblies in release mode but for the page compilations you may also need to edit the debug attribute of the compilation element in your web.config.
<compilation defaultLanguage="c#" debug="true">
Web applications do strange things when debug=true is set, for example they do not honor request timeouts because it would interfere with debugging.
Here is a great article from the Gu on the subject: Don’t run production ASP.NET Applications with debug=”true” enabled
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.
Closed 11 years ago.
The latest link I can find is from last may and that's Beta 1. Did Microsoft give up on this? I realize they are just basically MSBuild templates, but curious nonetheless.
Visual Studio® 2010 Web Deployment Projects - RTW
Web Deployment Projects are going forward in VS2010 - which is good news since web packages do not support Website projects
I hope they're not still alive.
We probably used them improperly so it's probably our own fault, but they caused us huge issues when we wanted to update just a portion of our site. The supposed benefits of using web site deployment projects never paid off for us and just caused more problems than they were worth.
Edit
Drats. They're still alive.
http://www.microsoft.com/downloads/details.aspx?FamilyId=0AA30AE8-C73B-4BDD-BB1B-FE697256C459&displaylang=en
I don't know about the web deployment projects, but here's something that's definitely alive: Web Deployment Tool (MS Deploy).
My guess is that they are packing this into Visual Studio 2010 . See http://blogs.msdn.com/webdevtools/archive/2009/06/28/vs2010-beta1-web-application-project-database-package-and-smo-options.aspx
The response from Microsoft:
Web Deployment Projects is not
currently planned to be part of VS
2010... As WDP is out of band we have not yet started planning on it as the
team is focused on working on VS 2010
at this point...
Looks like they've definitely shifted their focus onmsdeploy and "web packages."
I second David stratton - these things are the definition of half-baked. Good ideas wrapped in poor execution, the best thing I can say about them is that they aren't InstallShield.
I am working on an ASP.NET 3.5 project which has 55 projects in a solution. When opening the solution in Visual Studio 2008, it takes over a minute to open - about 1 second for each project. However, if I disconnect the network cable before opening the solution, it only takes about 15 seconds! Any ideas about what could be causing the slowdown?
I had this happen to me back in the days when we were using Visual Source Safe.
Could be your source control plugin asking for updates if you have the solution under source control.
You should do some investigation, fire up Wireshark, start a capture on the interface in question and see what traffic is flowing over the wire.
Can I answer a question with a question? What is the secret to getting VS to not just die with that many projects, let alone load in a phenomenally quick 60 seconds?
At about 10-12 projects the compile time on Visual Studio becomes unbearable, at about 5-8 projects Resharper will crash. The IDE is such a memory pig that even opening more projects by using multiple instances of VS usually isn't an option.
Anyhow, it's all about memory usage and the odd ball out project is probably doing it, e.g. the one with the most files.
I had the same problem this week (5 years later!!). It was caused by a huge .suo file (almost 400 Mb), deleting it fixed the problem.
A few years ago I remember a colleague having some similar problem (with a lot smaller solution, and in VS2003). Can't remember the details, but I think it was related to the local ASPNET user account (or rather, that it did not exist). Not sure though...
As a side note: I usually find it more efficient to have perhaps around a handful of projects in each solution (usually one solution produces one or two assemblies used in production code), and then have a few Visual Studio instances running at the same time. 50+ projects in the same solutions feels like asking for problems.
Might be that you have other dependencies though, just wanted to share my thoughts.
which has 55 projects in a solution
WOW. I can't imagine what type of solution needs that many projects. The answer is probably that your source control provider needs to refresh the status of each of the items, all of which take time.
For edit-merge-commit style version control systems, such as subversion, this operation doesn't take place. Try temporarily removing source control from the entire solution to see if this is the culprit.
If your solution is attached to source control, then it is trying to load up the symbols and verify which items you have checked out. So, if you have a slow connection, it is oftentimes faster to take the solution offline.
http://www.tmgirvin.com/2009/03/working-offline-with-visual-studio-2008-and-tfs.html
EDIT
Another solution which I've seen used,
create a
_webTier.sln
_database.sln
_build.sln
( is your project name)
and each of those solutions is a self-sufficient part of the entire project, but that way if you are working on the webtier and you don't need the database project or the mobile project parts to load up, you can just open the webtier solution.
The build solution contains the entire package that needs to be built, and takes a very long time to load.
I had this problem on a development machine with no internet connection and it turned out that the problem was related to a setting in IE's internet options:
Control Panel -> Internet Options ->
Advanced -> Security -> Check for
publisher's certificate revocation
After making sure this was unchecked my solutions started loading quickly again.