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 want to start using .NET 3.5 features in an app that is currently stuck in the past – how can I write in support for selected features like JSON serialization in a forward-compatible way?
In the case of JSON serialization I need to reference System.ServiceModel.Web – is it OK to reference a .NET 3.5 dll in a VS2005 app? Presumably this is in the GAC but on a deployment environment it may not be…
Referencing a .NET 3.5 DLL is not a good idea if your application targets .NET 2.0, as the library you’re referencing will likely reference other .NET 3.5 libraries that will not be available on a user’s computer if they do not have the .NET 3.5 runtime installed.
You can set your project to target .NET 3.5 if you like (from Project Properties|Application|Target Framework) which will overcome this problem – your app will then use its currently referenced .NET 2.0 libraries (as well as any .NET 3.5 libraries you want to add to use for new code), while requiring .NET 3.5 on users’ machines allowing the use of the DLL.