Whenever I update WCF service reference in front end project, the service reference update happens and the bottom left corner of Visual Studio indicates that the service reference update is complete, but Visual Studio becomes non responsive after the update. If I close the Visual studio using the Task manager and restart it, reopen the solution, I can proceed as normal and can use the updated service reference. For now I always restart my Visual studio and reopen my solution to continue working on my tasks. Has anyone faced this issue? If anyone found the solution for this issue, could you please help me fixing this as it is very annoying to restart the Visual studio every time I update the service references. Thank you.
(I am using Visual Studio 2013 - project uses .Net Framework, asp.net webforms, and C# as the language for development. - if it helps.)
After trying different options, I guess the size of sln file and the size of references caused the issue for me. We use Resharper in our company which adds extra load when updating the service references.
My Visual Studio doesn't hang/becomes not responsive (most of the times), when i do the following..
1) Go to Tools -> Options -> Source Control - change the default option from Microsoft Git Provider to None.
2) Tools -> Options -> Resharper Ultimate and disabl it.
3) Try to figure out which projects in the solution is not required or affected and unload them.
Then update the reference. Still sometimes it doesn't work for me, but most of the times i dont have to restart the solution using task manager. I always disable resharper before I have to update the service reference and enable it back again once the service reference is updated. Hope it help others if they face similar situations..
I am working on Sharepoint 2010 projects in Visual Studio 2010 and i am trying to attach to the w3wp.exe process. I attach fine and a few of my assemblies show up in the Modules pane, but the main assembly i want to debug does not. I have done everything to specifying the place to look for the pdb and even copying the pdb to a folder and pointing VS to look at that folder for the symblos but it still hasn't helped.
i have retracted and deployed
I have Cleaned all projs in the solution and then REBUILT and deployeed
I have rebooted
deleted bin and obj directories, cleaned, rebuilt and deployed
I don't know what else to try. I have tried things from posts all over the web, anyone have anything else to try. keep in mind this is a SHarePoint 2010 server with Visual Studio 2010 on it.
As Alex implied, it's not always intuitive to figure out when to attach to w3wp.exe, but as a general rule of thumb, if you're not actually watching the content getting rendered (that is, it's not in a web part or an application page), you almost always want to attach to the SharePoint Timer Service (owstimer.exe) instead. This is obviously true with stuff like timer jobs but it's equally the case with workflows and event receivers where you haven't explicitly called them as synchronous.
Alex's links are great for this too. I will add that when in doubt, and you're debugging out of your own dev environment, it's not always the worst thing in the world to attach to both owstimer and your application pool's version of w3wp.
in the end, someone over wrote the web.config changes required for the module so the code was never executed. It never had anything to do with the symbols. Thanks ULS for showing me the way ;)
Thanks for the responses.....
My intellisense and class highlighting does not work on one of ASP.NET website projects. It works for all other projects, including other ASP.NET website projects but just not this one.
The project was written in VS2010 and I've inherited it but am finding it difficult to use without code highlighting and auto-complete!
Note: my general VS2012 settings seem correct as I've never experience this with other projects loaded. I even created a new ASP.NET website project to check this, and yep, it all works fine in the new project!
If I type the first letter of a word that should be recognised e.g. the "S" of System then hitting ctrl-space gives me a list of options for logic operators, local variables, types such as:
for
myLocalVar
string
but no options for classes - so System doesn't appear, neither do any of my classes. If I do type out a class name in full then it will stay black and not be highlighted.
Here are two screen shots of the intellisense not working and the lack of highlighting. Any suggestions much appreciated!
It was actually an issue with my .suo file. This is the file that stores some user settings etc.
I deleted this file, and then re-saved the solution (.sln file).
Next time I opened the site I opened it using the .sln file instead of opening it as a web site:
File->Open->Project/Solution instead of File->Open->Web Site.
Hope this helps someone in the future.
A few questions, do you have ReSharper or any other development productivity tool that could have changed the settings for this particular project?
If not, then have you checked out the suggestions in this SO question?
Intellisense and code suggestion not working in Visual Studio 2012 Ultimate RC
What's the reason for error message "The snapshot is out of date and cannot be used anymore because type tree has been updated, A new snapshow needs to be acquired"?
This error appeared right after I launched VS2010 and added username/pwd to connect to TFS repository.
I am using VS 2010 professional edition.
It happened to me with VS2012 as well after loading the project without source control binding, a local simple WinForms project. All I needed to do was Clean & Rebuild. After that the problem was solved.
This is a bug in Visual Studio. According to http://connect.microsoft.com/VisualStudio/feedback/details/742959/the-snapshot-is-out-of-date "We've taken a closer look at this problem and it isn't one that we'll be able to solve in the next release of Visual Studio."
They recommend waiting around until the background language parser service is done (or, in other words, don't try to be too productive there partner.) My experience is that closing all documents, cleaning the solution, rebuilding it and then closing and re-opening with a pause after does remove the error.
Until you do something silly, like edit code. Then all bets are off again as to when it reoccurs.
I had a similar issue with VS2012 and after rebuilding the solution twice, I still saw the same error message.
Following an advice from a post from this site, I closed the Designer tab, reopened it from the Solution Explorer, and the problem was resolved.
I got this error too, but after I unload project and reload project, the problem was resolved.
Simply restarting Visual Studio 2012 was a workaround for me, but it kept happening about every hour and having to restart visual studio that often was very annoying.
I also found this post which suggests that the Productivity Power Tools are the problem and to simply turn off the Automatic Brace Completion in Tools->Options->Productivity Power Tools. Since making this change I haven't seen the error message again :)
I'll note though that I am using Visual Studio 2012 and the OP is using Visual Studio 2010, but the Productivity Power Tools are available for VS 2010 too, so this may still fix the problem in VS 2010.
The same issue persists in VS2013, but no amount of Clean/Rebuild or restarting VS will help. The only way I can do a successful publish, is to disable the AutoT4MVC extension.
I got this error too. I closed Visual Studio 2012 and opened it again and the error was gone.
I got this error when I had conflicting class names / namespaces. I was referencing a UserControl from a different DLL in my XAML file which had the same name as my XAML file (class name). Maybe this helps.
I used Visual Studio 2012, and just faced this error on my Windows 8. It seems like Turning off the VM and restarting Visual Studio fixed the issue.
I just got this with VS2010.
I had a form with a user control (UCa) with a user control (UCa) from a different project on it. Made a change to the UCb then flicked to the designer for the form and boom! Snapshot error.
Resolved by a full clean and then rebuilding just the UCb project before building the rest of the project.
I'm using Visual Studio 2012, and I got this error when starting Visual Studio, letting TFS connect to the server, and THEN opening my solution. The fix was simply closing VS and launching the solution directly.
I'll throw my two cents in here as well.
I've tried every combination of Clean, Rebuild, Restart, etc. What I've found is that restarting Visual Studio usually makes the problem go away for at least one Publish. Here's the weird part, though. You can also fix the problem by doing absolutely nothing. If you just let Visual Studio sit for about a minute or two, and then publish, it will usually work just fine. There's some background voodoo going on here, and waiting for it to finish seems to do the trick.
I have a solution with two parts that need published. One is a WCF service application, and the other is the ASP.NET MVC5 website itself. Anytime I publish the services, and then try to publish the site I'll see this error. I can publish the services, restart VS, and then publish the site, OR I can publish the services, go get a drink, and then publish the site. As long as I give VS a chance to "settle" between any kind of rebuild and the publishing of the site, everything seems to work as expected.
Take a walk, come back, problem solved. OR if you don't have the time. Clean, Rebuild, Restart, Publish (lather, rinse, repeat).
Im using VS express web developer, and attempting to create a new MVC project. The problem is, VS hangs when adding EntityFramework to the project. Its attempting to add EntityFramework 4.1.10331.0 to an MVC 3 project. Any ideas what might be going on?
It has been a while since you asked the question, but I recently stumbled across a similar issue except with MVC4 adding EntityFramework.5.0.0 in Visual Studio 2012 Ultimate.
The issue was that I was trying to create the project in a network folder (I run Windows 7 in a VM on top of OSX).
The problem appears to be that the network folder is not considered a Trusted Location. I had to go into Control Panel -> Internet Options, click "Security" tab, Click "Local Intranet" zone, then click Sites button.
In the "Local intranet" dialog which pops up, I un-checked "Automatically detect intranet network" and checked "Include all network paths (UNCs)"
Now I guess Visual Studio and/or nuGet see the network folder as a trusted location, and EntityFramework.5.0.0 is installed along with everything else a new MVC 4 project requires.
Credit goes to my colleague who referred me to this SuperUser post.
Bit of an old question, but it's still an issue today so this might help someone looking for a solution.
I don't have enough rep to comment on Chris Cameron's answer, so apologies for submitting it as a new answer - all credit should go to Chris. I found that to get it working I also needed to check "Include all local (intranet) sites not listed in other zones." Chris' solution then worked like a charm.