What to consider when upgrading from Visual Studio 2005 to 2008?

We plan to upgrade our developers from Visual Studio 2005 to 2008. Are there any common "gotchas" to search during this step?

My main task at the moment is that we use WSE 3.0 quite a bit (mainly for using external .asmx web services, but we also accept a few of ourselves). Would this be a problem since WSE 3.0 has been replaced by WCF?

Additional background information: VB.NET application with multiple websites, not web applications. .NET 2.0 is currently being used with plans to upgrade to 3.5 in the near future.

Should anything else bother us?

+3
source share
3 answers

I think the main issue you should be following is updating the commands. After upgrading to the new version of Visual Studio, you will also have to update the project files. When the upgrade is complete, the file will no longer be compatible with previous versions of Visual Studio. This means that you will break anyone who uses a previous version of VS for development. The best advice is updating the whole team.

- 2 . Visual Studio, . , , . , , , , Visual Studio.

+2

, ASP.NET( ), .

0

VS05-08 . 2005 VS2008, , . VS2008 "" .NET, , .NET 2.0. , 3.5 , .NET 2.0 , 3.5 ( ). , WSE " ".

, , .., . - - - , , .

In the end, just backup everything, then open in VS2008 and see what happens.

0
source

Source: https://habr.com/ru/post/1706480/


All Articles