CODEWITHSUNDEEP
c#asp.net
user1640256
user1640256

Reputation: 1719

Replacing old DLL with new DLL

My client lost the source code of their web application and wanted to make few small changes to it. I used RedGate's .Net Reflector to extract the source code from the DLL. Using the class files generated I was able to make changes at the desired place and re-generate the DLL. The application pool used by the application is "default" with version 1.1 and I think the application was also created using .Net framework 1.1, but I used visual studio 2008 to open the project and create the new DLL. also the old DLL had some version number. My question is: since the application is already online, will replacing the new DLL create any problem? Since the time frame given to us to replace the DLL is very small as the application can not stay offline for long, I want to make sure that everything goes fine. Am I following the right way? Or, do I have to create the new DLL using the same framework(1.1)? What else do I need to do to keep the application running smooth without any problem. Kindly excuse me for this lame question but this is the first time I am in this sort of scenario. Thanks.

Upvotes: 0

Views: 3230

Answers (3)

Prahlad Yeri
Prahlad Yeri

Reputation: 3663

While re-building your DLL, you need to ensure two things:

[1] The target framework of the project is the same as the one where you will be deploying it. You may check the currently targeted framework version from project->properties. If your live server has only 1.1, then so should be your target set in the project file.

[2] Need to ensure that all dependencies are met. You can see all dependencies from the References in solution explorer.

Upvotes: 2

Echilon
Echilon

Reputation: 10264

If there's anything else which references this DLL, you'll likely need to decompile/recompile that as well as the public key will more than likely change if you deconstruct the source. You should be safe to just copy it over, which will trigger a restart of the app pool.

Upvotes: 1

Mike Perrenoud
Mike Perrenoud

Reputation: 67918

To limit the issues you encounter you need to build the assembly against the 1.1 framework. Then, during the down window:

  1. Stop the application pool.
  2. Replace the assembly.
  3. Restart the application pool.

Upvotes: 0

Related Questions