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.
We have several applications written in Visual Studio 2005 that are deployed onto our servers. If we deploy applications written in Visual Studio 2008 on the same server will it cause DLL conflicts?
We want to ensure that upgrading our version of Visual Studios will not break existing applications.
Thank you.
This is one of those classic “it depends” answers based on the setup. Are you compiling the applications with .NET 2.0 in Visual Studio 2008 or are you targeting a newer framework? Do the DLLs get stored in a shared location (ie., the GAC — Global Assembly Cache) or are they stored in the application folder?
.NET 3.5 is backwards compatible with .NET 2.0 so you can easily reference 2.0 dlls to a 3.0 or 3.5 application but the reverse is not true.
If you are storing shared DLLs in the GAC you might have conflicts but just make sure the 2.0 and 3.5 versions of the DLLs have a different version and then you will avoid said conflicts.