What are the steps I should do and everything I should consider when upgrading from Visual Studio 2005 Team Suite to Visual Studio 2010 Ultimate?
Where can things go wrong?
Consider the fact I'm using TFS 2008 and have Continuous Integration and Nightly Builds on build machines.
One big Problem are Unittests with autocreated Private Accessors. If you want to touch them you have to rewrite them...
The issue is described Here
Related
We have an old MVC2 project stranded in Visual Studio 2010 and assigned to TFS 2010.
Is it possible to copy this project into VSTS and access VSTS in Visual Studio 2010?
Because it is an old project there is no need to migrate the version history.
What are my options?
Yes, you can access Visual Studio Team Services (VSTS) from Visual Studio 2010, however, you will need two software updates:
Visual Studio 2010 Service Pack 1 (KB2736182)
TFS 2012 compatibility update for Visual Studio 2010 (KB2662296)
Having said that, upgrading to Visual Studio 2017 is preferable if you can do that.
To bring your data into VSTS, the easiest way to do that is to use the TFS to VSTS migration tool, which providers an easy, high-fidelity migration into the cloud. However, since you don't require history, you can also perform a manual migration, where you simply check your assets into TFS directly.
I recently got a copy of Microsoft Test Professional 2013, where previously I used Visual Studio 2012. I'm unable to run any projects within Visual Studio 2013 - Shell Integrated, which comes with Test Professional 2013.
The development team have upgraded to Visual Studio 2013 with no issues and we have tried changing the project versions.
I have checked that I have the correct .net framework and mvc installed.
Should I be able to open the projects and if so what might be going wrong?
Is it safe to install TFS 2012 where some Visual Studio 2010 dev machines are still present?
Thanks.
You can use VS 2010 with TFS 2012, but you need to install SP1 and a GDR. See the compatibility matrix for more information.
You won't be able to use the new features (like code review) nor create new team projects though.
One of our TFS 2010 requirements is to support software projects that still use Visual Studio Team System 2008 for development. My question is whether a Build Server based on Team Build 2010 can compile 2008 code by itself. I mean connecting to TFS 2010 using Visual Studio Team Suite 2008, which means we are planning to install the Forward Compatibility Update on all development machines.
We have an existing TFS 2008 system and according to that the build server requires VSTS 2008 to be installed in order to compile code and run automated tests. I would assume the same for TFS 2010 where VS 2010 Ultimate should be installed in the build server, but we are not sure whether VSTS 2008 is required "as well" in this use case.
I hope someone could share their thoughts about this. Thanks.
As long as you install;
Visual Studio 2008 Team Suite,
Visual Stduio 2008 Team Explorer
VS2008 SP1
and 2008 GDR forward compatibility pack next to Visual Studio 2010 on the buildserver, Team Build 2010 can compile and unittest 2008 solutions. There are however some known issues with Workflow projects, so install VS 2010 and TFS 2010 SP1 and test your solutions.
I have several wdprojects (web deployment 2008) in vs2008 solutions.
When I installed vs2010 RC none of my wdprojects will open.
What can I do to make it work?
Visual Studio 2010 Web Deployment Projects RTW is available here: Visual Studio 2010 Web Deployment Projects RTW
Update:
As per this SO question, Visual Studio 2012 does not have Web Deployment Projects.
But it's ok: Visual Studio 2012 Web Deployment Projects are Dead – Long Live Publishing Profiles
According to this post on the ASP.NET forum they will actually provide support for it some time after the release of Visual Studio 2010. But I can confirm that it is not supported out of the box in the Visual Studio 2010 RTM.
Note there could also be some conflicts/warnings or errors when migrating.
Something like:
"Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive"
Here is an article which explains how to fix that:
http://extremedev.blogspot.com/2011/10/migrating-wdproj-from-vs-2008-to-vs.html
VS 2010 convertor will convert the project as required when you try opening it in VS2010.