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 have an ASP.NET application that uses a custom .NET library (a .DLL file). That .DLL file is strongly named. The library has frequent small updates, and I would like to be able to update this .DLL without recompiling the application. The application has to be precompiled because I do not want to give the source of it to my customers (not that it can’t be decompiled, but that’s besides the point).
Can this be done somehow? Currently I just get an error that the .DLL is of the wrong version.
You can supply them with an updated config file to go with the new dll. This config needs to have a custom version policy redirecting requests from one dll to the other. See this article for more information.
Actually this article has more information on the whole process and the different levels that you can define a version policy at.