Running ASP.NET v1.1 and v2.0 websites on the same server

Discussion in 'C#' started by webcosmo, Jun 23, 2007.

  1. #1
    Can we run both 1.1 and 2.0 web projects on the same Windows 2003 server? The answer in short is yes.

    IIS 6.0 can run both ASP.NET 1.1 and 2.0 web applications simultaneously on the same server, if each version specific application is assigned a different application pool. Now what is an application pool?

    Click the link for the complete solution:
    http://www.webcosmo.com/listing/Details.aspx?countryId=1&gId=1&postId=2748
     
    webcosmo, Jun 23, 2007 IP
  2. ccoonen

    ccoonen Well-Known Member

    Messages:
    1,606
    Likes Received:
    71
    Best Answers:
    0
    Trophy Points:
    160
    #2
    Yup, we mix and match app pools 1.1 and 2.0 all the time... I definitely prefer 2.0 though ;)
     
    ccoonen, Jun 25, 2007 IP
  3. newbish

    newbish Peon

    Messages:
    27
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    All you have to do is set the version in IIS.

    <website name> (right click)->properties->asp.net tab->asp.net version
     
    newbish, Jun 27, 2007 IP
  4. ProgrammersTalk

    ProgrammersTalk Peon

    Messages:
    684
    Likes Received:
    7
    Best Answers:
    0
    Trophy Points:
    0
    #4
    I use both :D
     
    ProgrammersTalk, Jun 27, 2007 IP
  5. webcosmo

    webcosmo Notable Member

    Messages:
    5,840
    Likes Received:
    153
    Best Answers:
    2
    Trophy Points:
    255
    #5
    Setting only the version wont work. At least didn't work in my case. I ran into this situation recently. First tried changing the ASP .Net version from the website properties. Didn't work, but my other sites running on .Net 1 version stopped working. Then I tried separating the worker processes for the .Net 2 version websites creating a separate application pool for them. That worked. However if you using AJAX on .Net 2, you have to do some more work e.g. copying some extra dlls for AJAX, change the web.config to fit the scenario.

    So far I like .Net version 2 except the Build Website creating dynamic dll names. That holds us reusing components among projects. Thats quite a bit of change from .Net 1.
     
    webcosmo, Jun 27, 2007 IP
  6. MasterOfLogic

    MasterOfLogic Well-Known Member

    Messages:
    217
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    103
    #6
    create separate application pools. put all your 1.1 sites in one pool. the others in the 2.0 pool. mixing them will cause errors! seen it 100 times.. usually when i start a new site and forget to change the asp.net version in IIS.
     
    MasterOfLogic, Jul 12, 2007 IP
  7. shrkscn

    shrkscn Peon

    Messages:
    1,157
    Likes Received:
    16
    Best Answers:
    0
    Trophy Points:
    0
    #7
    Version 2.0 is much better than 1.1. I love the hot deployment feature.
     
    shrkscn, Aug 4, 2007 IP