The result is that if one programmer within a team opens up a Visual Studio 2010 project using Visual Studio 11 and then checks-in the shared code after making changes, other developers on the same team can open up the same project using Visual Studio 2010 SP1 without any ramifications. The key is that the project files created by Visual Studio 2010 remain the same after opening in Visual Studio 11.
In contrast, Visual Studio 11 includes project compatibility as a specific feature, such that there's no project upgrade step. As a result, it became difficult for individual developers within a team to begin development with a newer version of Visual Studio without a plan for the entire team to upgrade as well. In the past, each release of Visual Studio modified the project files, sometimes only with a version number update. The rest of the article delves into the details of each of these improvements.ĭiscussion of installation and side-by-side development would normally be left until the end, but project compatibility in Visual Studio 11 makes upgrading to the new IDE so simple it's hard to ignore. Of course, Visual Studio 11 features don't just stop with integrated Power Tools. Storyboarding in Team Foundation Server 11.Visual Basic Improvements in Visual Studio 11.A Review of Visual Studio 11 Developer Preview.
Windows 8/Windows Server 8 Previews Released.New Project Types: Visual Studio 11 vs.More importantly, by building the extension functionality directly into the product, the integration is much deeper and cleaner. However, through Visual Studio 11, those extensions are built-in, eliminating the bother of installing and updating each one of those extensions.
Much of what's in the Visual Studio 11 IDE has been available for some time already in the form of Power Tools extensions to Visual Studio 2010. NET Framework additions and Metro-style development capabilities will be covered in future articles. Discussions of features such as language changes, Microsoft. Specifically, the focus is on new tooling included that's centered around productivity. In this article, I'll review what Visual Studio 11 has in store for developers from an IDE perspective. Here's your guided tour.īy the time you read this, Visual Studio 11 beta 1 will be available for download. Visual Studio 11 is packed with new features to help you be a more efficient, productive developer. ever freezing even though i program on a dell poweredge t605 server with a dozen gigs of ram and 2 3ghz chips.In-Depth Inside Visual Studio 11: A Guided Tour So just one more google had me find the ctrl+break solution above and now i can go back to my ever freezing vs 2010. when i saw some guy was reinstalling and registry spehlunkin' just to fix this i knew at a gut level he was caught in MSFT support hell: blah blah so I hit ctrl+break.Īnyway then the find in files got flaky as all pie crust and i found this site. I could not close VS but then it told me build is in progress you must cancel build before. In my case i was frozen and building and i really just wanted to overlay a folder as my site was hosed anyway and i was rolling back. Thanks for your help!Ībandon hope all ye who screw with registry.īefore you waste days cursing your VS BS please try the following:
Still baffled about all the 1402 messages, though, and also wished it was possible to restart a repair or install at different points, so I can skip the steps that it already succeeded in repairing or installing.
Since Find in Files was still not working, I tried your suggestion to delete the Find key from the registry and - lo and behold! - that fixed the Find problem - thanks so much for that! Got past those as well and was able to connect the Extension Manager. Since I had to restart (and reboot) the lengthy install after every failure, this took forever.Īt last it succeeded, but after starting VS it still complained about a few components. Something must have been wrong with the registry, because the repair threw up numerous error messages 1402 ("Setup cannot open the registry key: UNKNOWN\Components\.") which I fixed one by one by changing the permissions and ownership for Before I got your message I spent about 16 hours trying the "repair" VS2010 to see if that would solve the problem - also because I could not get the Extension Manager to connect to the Gallery anymore either.