CODEWITHSUNDEEP
asp.net.netvb.netdll
zod
zod

Reputation: 12437

What all things to consider on replacing a dll - vb.net aspx

I am new to .net and got a kind of weird migration work.

Due to circumstances i am going to change the functionality of 2 methods in a class and will build and create the dll. If i replace the old dll with new dll , will the application work and will it reflect new functionality in the server.

I am going to use same file name class name and methods .

What all things i have to consider on replacing the dll? and is it possible to just replace the dll ?

Upvotes: 1

Views: 108

Answers (1)

John Saunders
John Saunders

Reputation: 161821

Briefly, and in general, yes, you can just replace the DLL. That assumes:

  1. You have tested your new code in your Development and QA environments before promoting the changed DLL to your Production environment.
  2. You have a rollback plan in case something goes wrong when you deploy to Production
  3. Be aware that ASP.NET will allow all current HTTP requests to complete, but will create a new AppDomain in which to load a new copy of the web application, including the changed DLL. All subsequent requests will be handled by the new AppDomain. Among other things, this will mean that any static variables will be reset to their initial values, and depending on how you have Session state set up, your users may all lose their Session state. This may cause them to be logged out, depending on how you have implemented authentication.

Upvotes: 1

Related Questions