Using two .net versions?

[hertlessp]

Just a quick question is it possible to use both versions of .net(2.0.50727, 1.1.4322) on iis6? is there an application or coding that i have to apply to my II6 box? Is there a way of using them both at the same time?

[sirpelidor]

u can have both in the same machine, but I don't think you can have a piece of software that mixed the both of 'em as for back-end (sending msg through TCP/IP don't count).

for a single asp.net app, you can select the correct framework by going to IIS Management console, click"ASP.NET" tab, then click "Properties" of the virtual folder. There you can specify which version you want it to run with.

[hertlessp]

Thank you for the reply sirpelidor, but im trying to upgrade the iis 6.0 asp.net 1.4 to 2.0 and get this error message, "It is not possible to run two different versions of ASP.NET in the same IIS process. Please use the IIS Administration Tool to reconfigure your server to run the application in a separate process." Source:ASP.NET 2.0.50727.0 event:1062

any idea? how i can upgrade and resolve this
If i create a new application pool
Local error
Server Error in '/' Application.
---------------------------------------
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load type 'webdev3.Global'.

Source Error:

Line 1: <%@ Application Codebehind="Global.asax.vb" Inherits="webdev3.Global" %>


Source File: /global.asax Line: 1
------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210


External error
Server Error in '/' Application.
--------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

[A1ien51]

Look at: http://weblogs.asp.net/owscott/archive/2006/01/26/436607.aspx

Eric