Best practices for VS2005

uanmi · Post by **uanmi** » Thu Dec 01, 2005 12:39 am

I'm about to install VS 2005 on a computer that has VS2003 and I will also remove SQL 2000 and put SQL 2005, though this is used for websites and not the vault server.

I would like to know the best practices on how to migrate to this new environment. Should I move vault server to sql 2005? or can it remain on sql 2000?

Is there anything I need to do to ensure Vault works with both VS2003 and VS2005?

Is there a best practices document for this?
regards, Mark

lbauer · Post by **lbauer** » Thu Dec 01, 2005 8:30 am

We're working on a migration doc, but in the meantime:

Vault can continue to use SQL Server 2000.

Regarding VS.NET 2003 and VS 2005 -- are you planning to work in both IDE's, or will you be migrating your VS.NET 2003 projects to VS 2005?

uanmi · Post by **uanmi** » Thu Dec 01, 2005 5:34 pm

Hi Linda,

I still need to work in VS2003 for some projects and new ones will be in VS2005.

I would really appreciate your telling me if I can I migrate Vault Server to SQL 2005 Developer or should I leave it in SQL 2000? Is there anything to be gained by moving it?

I would really appreciate your migration and tips document when it is done.
regards, Mark

lbauer · Post by **lbauer** » Fri Dec 02, 2005 4:57 pm

You should be able to work in both VS.NET 2003 and VS 2005, as long as you don't use VS 2003 and VS 2005 for the same project. Also, only have one instance of Visual Studio open at a time.

Vault supports both SQL Server 2000 and SQL Server 2005. I don't think there's much difference from Vault's point of view. If you have other reasons to migrate to SQL Server 2005, then certainly you can use it for Vault.