What is the cause of the error message? I am using VS 2010 Professional Edition

Question

What is the reason for the error message "The snapshot is out of date and can no longer be used because the type tree has been updated, new equipment is required"?

This error appeared immediately after starting VS2010 and the username / pwd was added to connect to the TFS repository.

I am using the professional version of VS 2010.

Answer 1

This happened to me and to VS2012, and also after loading the project without reference to the initial control - the local simple WinForms project. All I had to do was Clean and Rebuild. After that, the problem was resolved.

Answer 2

This is a bug in Visual Studio. According to http://connect.microsoft.com/VisualStudio/feedback/details/742959/the-snapshot-is-out-of-date "We examined this problem in more detail and we will not be able to solve it in the next release of Visual Studio" .

They recommend waiting until the background parser service is executed (or, in other words, do not try to be too productive a partner there). My experience is that closing all documents, cleaning the solution, rebuilding it, and then closing and reopening it with a pause after deleting the error.

Until you do something stupid, how to edit the code. Then all bets stop again when they are repeated.

Answer 3

I had a similar problem with VS2012, and after restoring the solution again, I still saw the same error message.
Following the advice from this site , I closed the "Designer" tab, reopened it from Solution Solution, and the problem was resolved.

Answer 4

I also got this error, but after I unload project and reload project problem was resolved.

Answer 5

Just restarting Visual Studio 2012 was a workaround for me, but it went on every hour and had to restart the visual studio, which was often very annoying.

I also found this post , which suggests that Power Tools is Power , and just turn off Auto-Complete in Tools → Options → Power Tools. Since this change, I have not yet seen the error message :)

Note that I am using Visual Studio 2012, and OP is using Visual Studio 2010, but Power Tools Performance is available for VS 2010 too, so this can still fix the problem in VS 2010.

Answer 6

I also got this error. I closed Visual Studio 2012 and reopened it, and the error went away.

Answer 7

The same problem persists in VS2013, but no amount of Clean / Rebuild or restarting VS will help. The only way to make publishing successful is to disable the AutoT4MVC extension.

Answer 8

I got this error when I had conflicting class / namespace names. I referenced UserControl from another DLL in my XAML file, which had the same name as my XAML file (class name). Perhaps this helps.

Answer 9

I used Visual Studio 2012 and just ran into this error in my Windows 8. It seems that turning off the virtual machine and restarting Visual Studio fixed the problem.

Answer 10

I just got this with VS2010.

I had a form with a user control (UCa) with a user control (UCa) from another project. Made changes to UCb, and then clicked on the designer for the form and boom! Snapshot error.

It was decided to completely clean and then restore only the UCb project before building the rest of the project.

Answer 11

I am using Visual Studio 2012, and I got this error when starting Visual Studio, allowing TFS to connect to the server, and THEN opens my solution. The fix was simply closing VS and launching the solution directly.

Answer 12

I'll throw my two cents too.

I tried every combination of Clean, Rebuild, Restart, etc. I found that restarting Visual Studio usually fixes the problem for at least one publication. However, the strange part. 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 work fine. There some kind of von-voodoo is coming here and waiting for its completion, it seems to be doing the trick.

I have a solution with two parts that need to be published. One is the WCF service application, and the other is the ASP.NET MVC5 website. Every time I publish services, and then try to publish a site, I will see this error. I can publish the services, restart VS, and then publish the site, OR . I can publish the service, go have a drink, and then publish the site. As long as I give Sun a chance to "settle" between any re-creation and publication of the site, everything seems to work as expected.

Take a walk, come back, the problem is solved. OR if you do not have time. Clean, rebuild, restart, publish (spread, rinse, repeat).