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.
Is dll versioning implemented differently in .NET 1.1 versus .NET 3.5? It seems I can mix and match older and new versions of dependent dll’s in deployed applications using .NET 1.1 but leads to problems when doing the same mixing a matching with dll’s running in deployed .NET 3.5 applications.
A lot of this is dictated based on the “useSpecificVersion” property that can be set on your reference. The general rule of thumb is that you can use a NEWER version of a referenced DLL, just not an older version.
If you have “UseSpecificVersion” set to true, it will force the application to use that version, and ONLY that version of the referenced DLL. This is a feature that has been in .NET all along.
Use Specific Version Example
If you build dll X with a reference to version 01.01.00.00 of Referenced assembly Y. Any use with a version other than 01.01.00.00 of assembly Y will result in a failure.
Standard Example
If you build a dll X with a reference to version 01.01.00.00 of Referenced assembly Y, you can use version 01.01.00.00 or later without issue.