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.
If you have a modular applicaiton that depends on its modules to be in seperate libraries ( dlls ).
What kind of Re-deployment
strategy would be good to follow?
The application is installed using the Setup Project that is available in Visual Studio.
I would like to avoid the copy and paste approach!
The easiest way to get around the copy and paste approach would be to deploy your application as a smart client application. This way you just put your new dll’s in one single place, and the next time each application is restarted it will download the new assemblies.