Migrating from 1.1 to 3.5 (Multiple Framework Versions running in Parallel)   

I will soon migrate several Web sites on our production server from .NET 1.1 
to 3.5.

The plan is to install the .NET Framework 3.5 on our existing production 
server. This means the server would have 1.1 and 3.5 installed and running 
in parallel.

My plan is to migrate one Web site at a time (create new NTFS structure, 
install the new 3.5 assemblies and other resources, define a new Web site in 
IIS with virtual directories pointing to the new NTFS structure, then update 
the domain name/header info in IIS to to route traffic to the new Web site 
when 3.5 version of the site is ready go live).

How can I specify which .NET Framework version each specific Web site is 
running against? (when multiple Framework versions are available on the 
server)... keeping in mind that the old 1.1 version of the site will need to 
remain live until the moment I switch to the new 3.5 version; and I'm doing 
this site-by-site.

Thanks.

date: Fri, 3 Oct 2008 16:07:46 -0700   author:   Jordan S.

Re: Migrating from 1.1 to 3.5 (Multiple Framework Versions running in Parallel)   

There is a version switcher utility:
http://www.denisbauer.com/NETTools/ASPNETVersionSwitcher.aspx

YOu can also hand switch libraries in IIS or run the aspnet_regiis tool with 
the -s flag.

-- 
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box!                               |
********************************************
"Jordan S."  wrote in message 
news:OqWcezaJJHA.4280@TK2MSFTNGP04.phx.gbl...
>I will soon migrate several Web sites on our production server from .NET 
>1.1 to 3.5.
>
> The plan is to install the .NET Framework 3.5 on our existing production 
> server. This means the server would have 1.1 and 3.5 installed and running 
> in parallel.
>
> My plan is to migrate one Web site at a time (create new NTFS structure, 
> install the new 3.5 assemblies and other resources, define a new Web site 
> in IIS with virtual directories pointing to the new NTFS structure, then 
> update the domain name/header info in IIS to to route traffic to the new 
> Web site when 3.5 version of the site is ready go live).
>
> How can I specify which .NET Framework version each specific Web site is 
> running against? (when multiple Framework versions are available on the 
> server)... keeping in mind that the old 1.1 version of the site will need 
> to remain live until the moment I switch to the new 3.5 version; and I'm 
> doing this site-by-site.
>
> Thanks.
>
>

date: Fri, 3 Oct 2008 18:54:22 -0500   author:   Cowboy \(Gregory A. Beamer\) oSpamM

Re: Migrating from 1.1 to 3.5 (Multiple Framework Versions running in Parallel)   

"Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in 
message news:#o7PQNbJJHA.1156@TK2MSFTNGP05.phx.gbl...
> There is a version switcher utility:
> http://www.denisbauer.com/NETTools/ASPNETVersionSwitcher.aspx

When you run the version switcher, you will notice that there is no "3.5" 
version. That's because there is no 3.5 version of ASP.NET. 3.5 uses the 
same .NET 2.0 CLR, so you will be switching from 1.1 to 2.0.
-- 
John Saunders | MVP - Connected System Developer

date: Fri, 3 Oct 2008 20:21:52 -0400   author:   John Saunders

Re: Migrating from 1.1 to 3.5 (Multiple Framework Versions running in Parallel)   

Good catch.

You, technically, will be running 3.5 only if you have 3.5 bits and the 
proper web.config file. That leads us to one more note. The web.config files 
for 2.0 and 3.5 are not completely compatible and you will need the 3.5 
stuff to run 3.5 apps. Fortunately, switching framework version in Visual 
Studio 2008 does a good job of fixing these inconsistencies for you.

-- 
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

Subscribe to my blog
http://feeds.feedburner.com/GregoryBeamer#

or just read it:
http://feeds.feedburner.com/GregoryBeamer

********************************************
| Think outside the box!                               |
********************************************
"John Saunders"  wrote in message 
news:OvzSpbbJJHA.1968@TK2MSFTNGP06.phx.gbl...
> "Cowboy (Gregory A. Beamer)" <NoSpamMgbworld@comcast.netNoSpamM> wrote in 
> message news:#o7PQNbJJHA.1156@TK2MSFTNGP05.phx.gbl...
>> There is a version switcher utility:
>> http://www.denisbauer.com/NETTools/ASPNETVersionSwitcher.aspx
>
> When you run the version switcher, you will notice that there is no "3.5" 
> version. That's because there is no 3.5 version of ASP.NET. 3.5 uses the 
> same .NET 2.0 CLR, so you will be switching from 1.1 to 2.0.
> -- 
> John Saunders | MVP - Connected System Developer

date: Sat, 4 Oct 2008 09:44:16 -0500   author:   Cowboy \(Gregory A. Beamer\) oSpamM