I am having trouble with creating tables in VS 2012 and cant seem to resolve this. I loaded Visual Studio 2012 Ultimate yesterday, didn't do any manual configuring just let it install. Couple of days later tried to add a table in my solution in Design view by right clicking the Tables icon in Server Explorer, and the error seen in the image below appeared, I thought it might be a problem with my solution so I created a another, and another, but still had the same problem.
Is this a known issue in VS 2012 Ultimate, or is there something I'm missing here? Is there a fix or a workaround?
go to programs and features of your windows as if you are going to uninstall VS and click repair.. it solved the problem to me
Related
I recently upgraded to Visual Studio Enterprise 2019 (version 16.0.3) and I have been having serious problems with autocomplete. It is so slow that I type faster than it is able to update, and frequently after I type out a complete and correct language keyword such as foreach the autocomplete drop down won't appear until moments before I press space which in many cases causes the keyword foreach to be corrected to some nonsense without warning.
This hasn't been a problem for me with any other version of Visual Studio going back to Visual Studio 97, and it is driving me nuts. I have no addons installed.
Is anyone else having this problem, and if so, what if anything were you able to do to resolve it?
You should open window defender then add exclusion folder for visual studio 2019.
I also add my folder source code.
Hope this help to who need
Hello I found that checking out this checkbox speeds ups VisualStudio InteliSence a lot...enter image description here
Upgrading to 16.1.4 seems to have resolved the problem.
Trying to install 'Visual Studio 2015 with Update 3' using the .exe installer provided for the visualstudio.com website. I also tried the standard version (without the update).
The black/grey installer opens, the green bar moves along the progress bar once and it crashes. I get a white pop-up window saying 'Microsoft Visual Studio Community with Updates has stopped working'.
I can't seem to find any other situations like mine on Google or StackOverflow.
I have Visual Studio 2017 also installed. Why do I need 2015 too? I'm helping (trying) another student who is using VS2015 and has problems - however, I can't even get it downloaded!
Thanks in advance for any help.
One possible solution is to not worry about 2015 and just help him by using 2017. It's hard to tell for sure if this will resolve your issue, as there is not info on exactly what you are trying to help him with.
If you go this route, I would save out the solution file just after loading it with _vs2017 tacked on the end, or something similar, so that you do not overwrite the info in his solution file. (Edit: The purpose of this is just in case it breaks something for him - it may not be a problem, he may be able to load your 2017 solution file fine). I've moved fluidly between 2017 Community and 2015 Express or Community with some solutions without a problem.
I do realize there are some issues that this may not be a solution for, but it should be an option, especially for those that are more language-based. The main problems with this solution would be if other student is using features or libraries that are deprecated in 2017, or directly struggling with getting VS 2015 features to work.
Go to control Panel -> Programs and features -> turn on windows features ,
Disable .net 3.5
check for windows update,
Then restart the system. Now it will work . 100% working .
Have fun.
Until quite recently it was possible to click on a method in the VS 2013 Solution Explorer and have the method appear in the code window. That does not appear to be working anymore. Any idea of how to enable this functionality? It was quite useful. For example, in the Solution Explorer view below, clicking on either addBlanks or formatSql would move the code window to the method in question.
It turns out that I have more information about this problem. I completely uninstalled VS 2013 Pro and reinstalled it. Somewhat predictably the problem went away... However, I was getting an error message about the NuGet package manager not being properly installed. To fix this I removed and reinstalled the NuGet package manager. That did resolve the NuGet error message, but the problem with clicking on methods in the Solution Explorer came back. Finally I removed and reinstalled VS 2013 Pro yet another time and now clicking on methods in the Solution Explorer works correctly.
Somehow the original problem reflects some combination of VS 2013 Pro, NuGet, etc.
It is still possible to quickly display a source code file. I am using Visual Studio 2013 Express Update 3.
It might make a difference to highlight/activate the right-most code preview symbol in the Solution Explorer panel:
It is located to the right of the properties screw-wrench symbol.
If this symbol is active, a single click on a file name is sufficient to get the file displayed in the code view. The same applies to methods. Double-click also works, when the preview symbol is not highlighted.
This turned out to be a bug in Visual Studio 2013 Pro Update 3 (and perhaps other versions). Microsoft recognized this bug and has fixed it in VS 2013 Pro Update 4. See https://connect.microsoft.com/VisualStudio/feedback/details/1001072/double-click-in-visual-studio-2013-update-3-solution-explorer-not-working for a discussion and Microsoft's resolution.
I'm having this error pop up once I start Visual Studio professional 2013 with update 3.
I don't know whats going on and also when I created a web form and try to put items from the toolbox into a table in my code it doesn't let me. the items are dim and can't select them any more. before I would make a table and try to add Labels, textbox, etc and it wasn't a problem.
Visual Studio 2013 Update 4
Tools -> Extensions and Updates
Disabled "Release Management for Visual Studio 2013 v2.1".
That worked for me.
I got the same issue today, but the error message should be giving you some guidance.
Take a look at mine, it tells me to check the "ActivityLog.xml" for more information.
After looking at the entry my error showed me that it ocured the evening before around 5:30pm and I know I was installing the Visual Studio 2013 Update 4 at this time. So it seems I had a problem with my Update installation.
(Sorry maybe someone can school me on how to properly load an image for viewing)
So I realized my problem was an install issue I created, yours might be an add-on or something similar that you just updated your Visual Studio with that corrupted your VS.
So a little more researching and asking some buddies at work and we tried doing this step in another SO article, which should have the same effect of fixing our package loading problem also.
the Provider package did not load.
After running the steps listed there my Visual Studio started up without any obvious issue.
Hope this helps.
Open ActivityLog.xml in a viewer (I've used Microsoft Edge) and you'll find the error. VSPackage is the "Developer Analytics Tools" extension for me.
The error is gone after uninstalling that package. You can obtain the package and attempt to reinstall from the Developer Analytics Tools page in the Visual Studio Gallery.
I uninstalled and reinstalled Visual Studio and the problem went away for a little bit. It eventually came back complaining about different packages.
Then I noticed my home directory was encrypted. I decrypted the directory and the problem went away.
If it is not an encryption issue, I'd try just uninstalling and reinstalling VS 2013.
Message could be shown in case of "Path" environment variable longer than 2048 characters. In that case, system doesn't work proply with system paths like %windir%.
If it's your case, shorten "Path" environment variable and everything works again.
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).