Project Compatibility in Visual Studio 11
- Posted: Dec 07, 2011 at 9:31 AM
- 32,061 Views
- 9 Comments
Backward compatibility of projects and solutions has always been a tricky issue for developers. Previously, if you built a solution in Visual Studio 2008 and opened it in Visual Studio 2010, you were presented with the Visual Studio Conversion Wizard. After running the Wizard, you could open your project in Visual Studio 2010, but you could no longer open it in Visual Studio 2008. Visual Studio 11 changes this. You can now open Visual Studio 2010 solutions in Visual Studio 11, work on them and then open them again in Visual Studio 2010. In this episode, Robert talks with two members of the Project Compatibility virtual team, Lisa Feigenbaum and Karl Burtram. Lisa and Karl discuss project compatibility in Visual Studio 11 and provide insights into how it works.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More episodes in this show
-
Visual Studio Toolbox: Telerik JustCode
-
Project Compatibility in Visual Studio 11
-
Visual Studio Toolbox: Performance Profiling
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
i was so excided when i heard about this feature, how ever i was even more dissapointed when it didnt actually work
To be more specific, it doesnt work if the vs2010 users have not installed SP1, and sadly(and inexplicably) this vs2010 sp1 is not available though windows update, even if you go through the help menu in vs and ask it to look for updates, its not found.... you have to download it manually
its so so sad that this great feature is made useless by the fact that vs2010 is not automatically updated to sp1 :/
@aL_: You can open a VS 2010 project in VS 11 without having to convert it even if you don't have SP1. SP1 is required if you want to make changes in VS 11 and then open the project again in VS 2010.
I'm not sure I understand why having to manually download SP1 makes any feature useless.
Robert
@aL_:And by the way, VS 2010 SP1 is available through Windows Update.
I too was super excited about this, but also very disappointed as it won't work for our solution either since we use a Team Foundation Database Project (.dbproj), which is not backwards compatible with VS 11; VS 11 still gives us a conversion wizard and wants to convert it into a new type of database project
@deadlydog:
It can work for database projects -- If you go ahead with the upgrade of the .dbproj, you can then do database project development in VS11 and roundtrip the new project with VS2010 with SQL Server Data Tools (SSDT). The .dbproj will upgrade to .sqlproj, which is the database project type of SSDT, and the .dbproj artifacts will be backed up. SSDT is replacing Team Foundation Database Projects in VS11, and is also available to install on Visual Studio 2010, free from the web here: http://msdn.microsoft.com/en-us/data/tools.aspx . You can fully roundtrip the SSDT Database Projects (.sqlproj) between VS11 and VS2010 if you install SSDT on VS2010. There are a few .dbproj sub-artifacts that will not upgrade because they are not supported in VS11 at this point, including data generation plans and database unit testing. Check out the link above for more info about SSDT!
well yeah... but thats not really backwards compability though is it.. The whole point is to be able to go back and forth between VS2010 and VS11.
Not having VS auto update itself nor via windows update [and i just checked again on several coworkers machines and SP1 does not show up on win update, even if external updates are enabled] makes the backwards compat useless in practice since anyone actually using vs11 will have to go around, manually convincing every other developer to manually update, a process that can take something like 30-45 minutes. That just not going to happen..
This is a great feature, its just a shame the lack of properly woking update infrastructure in vs2010 limits its use in small teams and makes it impossible to use in larger teams.
Visual Studio 2010 SP1 is definitely on Windows Update, I just applied it to a new laptop I setup. Does your organization have a federated WSUS server? If so you may have to click on "Check online for updates from Microsoft Update" to get updates which your WSUS administrator hasn't enabled locally.
need help in project ... subject is "cable operating system"....... in vb.net 08.... pakeges form is very tuff to design
@briankel:
Thats really odd, it has never shown up for me at home or at the two diffrent companies ive worked at for the past five years and i know for a fact wsus was not enabled on two of these places.. Maybe its a regional thing, Sweden still get Bing beta(!!) unless you manually go in and change the language to en-us
anywhoo, its a great feature! as long as everyone has sp1
Remove this comment
Remove this thread
close