Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am currently working on a project that is moving from .NET 2.0 to 3.5 across the board.
I am well aware that 3.5 is basically a set of added functionality (libraries, if you will) on top of what 2.0 offers.
Are there any gotchas that I might hit by simply re-targeting the compiler to 3.5?
This isn’t a gotcha, it’s more of a heads up. .NET v3.0 and v3.5 are not new CLRs but simply an added set up assemblies, compilers, resources etc…
Both .NET v3.0 AND v3.5 use the v2.0 CLR. Because of this you won’t be able to say set an IIS App Pool to use a v3.5 CLR…cause it doesn’t exist.
Discussed in a little more detail here: http://www.hanselman.com/blog/HowToSetAnIISApplicationOrAppPoolToUseASPNET35RatherThan20.aspx