Are there any dangers when using Visual Studio 2010 to develop .net 3.5 sp1 products?

We are pleased to be able to update our IDE development from Visual Studio 2008 to 2010. However, in the near future, our production environment will not be upgraded from .net 3.5 sp1 to .net 4.0.

What are the possible risks when using Visual Studio 2010 to develop production-class applications that will run on .net 3.5 sp1?

+3
source share
3 answers

Only a small issue that I know of. The new C # project created in VS2010 will depend on Microsoft.CSharp.dll, the runtime support assembly for the new β€œdynamic” keyword. When you change the version of the target environment to 3.5, you will receive a warning about this assembly, you must remove it manually.

In addition, your code will be compiled by the new C # 4.0 compiler, even if you aim for an earlier version of the framework. This may be the source of a compatibility issue, code that compiles differently with 3.0 compiler. A more common compatibility issue is code that should not compile in version 3.0, but because of a compiler error. Of course, not a real problem, but there may be a byte if you check the code that was written by team members who are still using 3.0

, 4.0 Project + Properties, Build, /, Advanced, Language Version = "# 3.0".

, connect.microsoft.com.

+4

. , , , - 4.0, , "svn revert".:)

, , , MSBuild VS 2010. MSBuild 3,5 , .

+3

3.5 ( 3.0 2.0) - , 2008 . , , 2.0, 3.0 3.5 .

- - .

0

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


All Articles