Releasing updates to virtual directory

Discussion in 'ASP .Net' started by McGeeky, Sep 1, 2005.

  1. McGeeky

    McGeeky Guest

    Are there any best practices on releasing updates of an ASP.Net application
    to a virtual directory in a production environment? E.g. is it okay to
    simply copy over changes to ASP.Net pages in to the virtual directory whilst
    IIS is still running or should IIS be stopped first?

    --
    McGeeky
    http://mcgeeky.blogspot.com
     
    McGeeky, Sep 1, 2005
    #1
    1. Advertising

  2. Hi McGeeky,

    Well, first it depends on how your ASP.Net app is structured. Are you using
    compiled DLLs or simply text files (.aspx, .asmx, etc)? If using compiled
    DLLS, are you using a single DLL, or an app DLL and class library
    assemblies? And what exactly are you replacing? Only Page template files,
    DLLs, or both?

    If you are replacing only text files, you may be able to get away with
    replacing the text files while the app is running. However,
    interdependencies between pages may cause some logged-in users to experience
    exceptions if they are using any pages that are interdependent with other
    pages that are changed, or if they are using pages that you replace that are
    interdependent with unchanged pages.

    If you replace the web.config file, or the dll, the app will restart, and
    this may cause problems with logged-in users as well, as it kills all
    current Sessions, and re-initializes the application. In fact, you might
    just as well expect that in almost any scenario, you may cause problems for
    currently logged-in users.

    Of course, restarting IIS, or an application pool (in IIS 6) is going to
    have the same effect, so in either case logged-in users are going to
    experience difficulties.

    So, the most important thing to keep in mind is to make changes when there
    is as little traffic on the site as possible.

    --
    HTH,

    Kevin Spencer
    Microsoft MVP
    ..Net Developer
    Neither a follower nor a lender be.

    "McGeeky" <> wrote in message
    news:...
    > Are there any best practices on releasing updates of an ASP.Net
    > application to a virtual directory in a production environment? E.g. is it
    > okay to simply copy over changes to ASP.Net pages in to the virtual
    > directory whilst IIS is still running or should IIS be stopped first?
    >
    > --
    > McGeeky
    > http://mcgeeky.blogspot.com
    >
    >
    >
     
    Kevin Spencer, Sep 1, 2005
    #2
    1. Advertising

  3. McGeeky

    McGeeky Guest

    That is really useful advice, thanks Kevin!

    --
    McGeeky
    http://mcgeeky.blogspot.com


    "Kevin Spencer" <> wrote in message
    news:...
    > Hi McGeeky,
    >
    > Well, first it depends on how your ASP.Net app is structured. Are you
    > using compiled DLLs or simply text files (.aspx, .asmx, etc)? If using
    > compiled DLLS, are you using a single DLL, or an app DLL and class library
    > assemblies? And what exactly are you replacing? Only Page template files,
    > DLLs, or both?
    >
    > If you are replacing only text files, you may be able to get away with
    > replacing the text files while the app is running. However,
    > interdependencies between pages may cause some logged-in users to
    > experience exceptions if they are using any pages that are interdependent
    > with other pages that are changed, or if they are using pages that you
    > replace that are interdependent with unchanged pages.
    >
    > If you replace the web.config file, or the dll, the app will restart, and
    > this may cause problems with logged-in users as well, as it kills all
    > current Sessions, and re-initializes the application. In fact, you might
    > just as well expect that in almost any scenario, you may cause problems
    > for currently logged-in users.
    >
    > Of course, restarting IIS, or an application pool (in IIS 6) is going to
    > have the same effect, so in either case logged-in users are going to
    > experience difficulties.
    >
    > So, the most important thing to keep in mind is to make changes when there
    > is as little traffic on the site as possible.
    >
    > --
    > HTH,
    >
    > Kevin Spencer
    > Microsoft MVP
    > .Net Developer
    > Neither a follower nor a lender be.
    >
    > "McGeeky" <> wrote in message
    > news:...
    >> Are there any best practices on releasing updates of an ASP.Net
    >> application to a virtual directory in a production environment? E.g. is
    >> it okay to simply copy over changes to ASP.Net pages in to the virtual
    >> directory whilst IIS is still running or should IIS be stopped first?
    >>
    >> --
    >> McGeeky
    >> http://mcgeeky.blogspot.com
    >>
    >>
    >>

    >
    >
     
    McGeeky, Sep 1, 2005
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Jack Wright
    Replies:
    1
    Views:
    489
    sonikchopra
    Apr 19, 2005
  2. Steve Singer
    Replies:
    0
    Views:
    563
    Steve Singer
    Feb 15, 2005
  3. Dave
    Replies:
    1
    Views:
    9,851
    Steven Cheng[MSFT]
    Oct 24, 2005
  4. =?Utf-8?B?SmVmZiBCZWVt?=

    physical path to virtual path under virtual directory

    =?Utf-8?B?SmVmZiBCZWVt?=, Aug 1, 2007, in forum: ASP .Net
    Replies:
    4
    Views:
    1,091
    Eliyahu Goldin
    Aug 1, 2007
  5. rockdale

    include virtual in virtual directory?

    rockdale, Sep 3, 2008, in forum: ASP General
    Replies:
    3
    Views:
    473
    rockdale
    Sep 4, 2008
Loading...

Share This Page