ASP.NET and framework 1.1

[Luc Bisson]

We recently installed framework 1.1 on our development
machines. We use framework 1.0 to compile our .NET
application because we still use VS 2002.

On MSDN, it is stated that the ISAPI filter used upon
installing framework 1.1 is the ASP.NET_1.1.4322.573,
which is true. Since then we had a problem with our site
using CMS.

So on particular sites we prefer running our applications
with the framework 1.0 As stated on MSDN, we rolled back
to the old ASAPI filter (ASP.NET_1.0.3705.288) for those
sites.

To my surprise, the framework 1.1 is still executing on
those processes even after rebooting the workstation.

What are we doing wrong in rollbacking to the old ISAPI
filter.

Any idea?

 

[Cowboy \(Gregory A. Beamer\)]

If you used the aspnet_regiis method, you should see that the website in
question is mapped to version 1.1. You will have to open the Internet
Services Manager tool and look at the Application Configuration (Home
Directory tab for sites, Virtual Directory tab for Virtual Roots, then hit
Configuration). Check the mappings for .aspx, et al. If it is not pointing
to 1.0, you can either type it in for each mapping (tedious) or use
aspnet_regiis.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnhcvs03/html/vs03f6.asp

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

**********************************************************************
Think Outside the Box!
**********************************************************************

 

[Dmitriy Lapshin [C# / .NET MVP]]

Hi,

1. Amend the web.config file to establish correct assembly version redirects
(VS .NET 2003 can do this for you when you turn on support for both versions
of the framework in the web project's options).

2. Use the aspnet_regiis.exe tool (not sure of the filename) from the
1.0.3705 folder in the Microsoft .NET folder to register the right ASP .NET
handler for a website or for a virtual directory.

 

[Luc Bisson]

It worked fine with the aspnet_regiis.exe tool. Thank's a
lot.

-----Original Message-----
Hi,

1. Amend the web.config file to establish correct assembly version redirects
(VS .NET 2003 can do this for you when you turn on support for both versions
of the framework in the web project's options).

2. Use the aspnet_regiis.exe tool (not sure of the filename) from the
1.0.3705 folder in the Microsoft .NET folder to register the right ASP .NET
handler for a website or for a virtual directory.

--
Dmitriy Lapshin [C# / .NET MVP]
X-Unity Test Studio
http://x-unity.miik.com.ua/teststudio.aspx
Bring the power of unit testing to VS .NET IDE

We recently installed framework 1.1 on our development
machines. We use framework 1.0 to compile our .NET
application because we still use VS 2002.

On MSDN, it is stated that the ISAPI filter used upon
installing framework 1.1 is the ASP.NET_1.1.4322.573,
which is true. Since then we had a problem with our site
using CMS.

So on particular sites we prefer running our applications
with the framework 1.0 As stated on MSDN, we rolled back
to the old ASAPI filter (ASP.NET_1.0.3705.288) for those
sites.

To my surprise, the framework 1.1 is still executing on
those processes even after rebooting the workstation.

What are we doing wrong in rollbacking to the old ISAPI
filter.

Any idea?

.

 

[Luc Bisson]

Thank's for the infos.

-----Original Message-----
If you used the aspnet_regiis method, you should see that the website in
question is mapped to version 1.1. You will have to open the Internet
Services Manager tool and look at the Application Configuration (Home
Directory tab for sites, Virtual Directory tab for Virtual Roots, then hit
Configuration). Check the mappings for .aspx, et al. If it is not pointing
to 1.0, you can either type it in for each mapping (tedious) or use
aspnet_regiis.

http://msdn.microsoft.com/library/default.asp? url=/library/en-us/dnhcvs03/html/vs03f6.asp

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

********************************************************** ************
Think Outside the Box!
********************************************************** ************



.