mkruer

Right now we are in the process of upgrading our entire environment. Part of this is to use the new bug tracking and source control features inside of Team Systems. The problem is that we have a lot of projects that are VS2003 projects, and it will be impossible to migrate them to VS2005 quickly.

We would like to use Team Systems to manage our VS2003 projects without having to migrate them to VS2005 yet. Is this possible, if so how Also when we run TFS builds, can we specify what compiler version to use Some DLLs are still using the 2003 compiler, so I want to make sure we can handle these.

Thank you

-Matt-



Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

Richard Berg MSFT

Yes, you can use source control from within VS2003. http://www.microsoft.com/downloads/details.aspx FamilyId=87E1FFBD-A484-4C3A-8776-D560AB1E6198

For work items, builds, reports, etc you'll need to install the Team Explorer component at minimum. On machines without VS2005, this will just install a thin shell. On machines with VS2005, it will integrate the Team Explorer pieces into the main IDE.

To make msbuild (and thus Team Build) use the old compilers, check out "MSBee."




Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

mkruer

Just to make sure I understand you correctly. The developers have 2003 and 2005 installed on their system. This will give VS2003 the ability to use source control via TFS, without VS2005 trying to force some type of migration upgrade, i.e. fixing syntax error that 2005 does not support, but were valid in 2003.

Also on the MSBee (http://www.microsoft.com/downloads/details.aspx FamilyID=e0d0776f-25c4-444a-a6b9-71d06826f5b4&DisplayLang=en) I assume that this will allow me to compile VS2003 source code in 2005 without as mentioned above having to correct the syntax in for 2003.

Thanks

-Matt-





Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

Michal Malecki - MSFT

Yes, Tfs Msscci provider let's you use Tfs from within the VS2003 without any changes,migration, problems from VS2005. It let you do most of the typical version control operations, to use WIT/Team Build/Reporting you need Team Explorer.




Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

Richard Berg MSFT

All the MSSCCI plugin does it let you access source control from inside the VS2003 IDE. It does not affect the compilers or the project files (makefiles) one way or the other.

For details on MSBee, I would ask in the MSBuild or Team Build forums. My understanding is it only works with the standalone msbuild.exe -- I don't think you can use it inside the VS2005 IDE.




Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

Bryan Hinton

As far as builds go - not sure all of what you are looking for here - but another way to make it work would be just to have the Team Build project shell out and compile VS2003 projects using the 2003 devenv. That would compile your sources without the complexity of MSBee - with MSBee I don't think you can feed it your 2003 project files and so you would have to maintain a separate project (whether a 2005 project or a MSBuild file - in the end they are basically the same) that catalogs the files needing compilation.



Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

mkruer

Thank you to everyone, I got the first part working. The final part if I can phrase it correctly, is I would like to know if I can use Team Build in 2005 to compile a 2003 project using MSBee without having to update the solution file The general idea is to be able to compile all projects in one location. We want to use the Team Foundation to track failed builds for the 2003 projects.

Thanks

-Matt-





Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

Paul Witt

I have this same issue I'm dealing with currently. We're setting up Team Build to compile our system and part of the code is in 1.1 and has to stay completely in 1.1. There has to be a way to have one Team Build that will compile both 2.0 and 1.1 code without converting our solutions to VS2005.





Re: Team Foundation Server - General VS2003 to TFS/VS2005 migration path.

mkruer

I am moving the second part of the question to a new thread at http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1599188&SiteID=1&mode=1