Comments on: .NET Framework 1.1 and 2.0 Side-by-Side (SxS)

By: senthil kumar

senthil kumar — Wed, 07 Jan 2009 09:43:06 +0000

Very useful information.

now i can run framework1.1 and 2.0 web applicagtion on same iis6 server.

what i did

1.I Created new application pool

2.This application pool configurated on my application website (framework 1.1)

3.I added following code on web.config

4. set aps.net version 1.1 in my web site.

Thanks

senthil Kumar

esenthil.erd@gmail.com

By: Pasmado

Pasmado — Sat, 02 Aug 2008 07:28:33 +0000

Hi. I have an strange problem. I have a Windows Server with a little processor (1 GHz). Before the instalation of the .NET Framework 3.5 the server had some Web applications in classic ASP and ASP.NET 1.1. The server was fine. I created the pool aplication and puted an 2.0 framework web aplication here. This web site has become unpredictable. Sometimes the user see in his browser that no error is displayed, but an infinite load appear. The fist page of the site never load in the client. No errors reported in the server’s event viewer. I suspect that this is a machine’s resources problem, or may be I need an special configuration for the 2.0 framework application pool. What is the minimum hardware requirements to run the 3.5 framework? How I can configure the application pools in a limited CPU processor scenario?

By: Durga

Durga — Thu, 03 Jul 2008 12:06:03 +0000

Hi Thomas,

It’s a very nice article pointing to the solution directly. It saves lot of time.

I have a quick question for you. We have project where we show the .Net Windows user control developed in 1.1 framework in Internet Explorer. The web application is deployed in webserver and the clients access it from their machines.

If the client machine has both 1.1 and 2.0 frameworks installed, browser is trying to load the control using the framework 2.0 which is not acceptable in our case. If we create the config file ‘IEXPLORE.EXE.config’ with the ‘supportedRuntime’ parameters, it is working fine and loading the control with 1.1 framework.

The problem here is, our client doesn’t accept this solution and doesn’t want to create this config file in all the client machines.

Is there any other way where we can specify that the browser should use only 1.1 framework to load our dlls.

Please help me out, if you know some way. Thanks in advance.

By: Edy Panyun

Edy Panyun — Mon, 12 May 2008 07:50:37 +0000

Thank you so much, now my framework 1.1 and 2.0 in Windows Server 2003 is working at the same time.

By: PGC

PGC — Thu, 20 Dec 2007 18:06:12 +0000

Nice. Thanks for the tips. I’ll definitiely look into those. Thanks!

By: Thomas

Thomas — Tue, 18 Dec 2007 01:09:30 +0000

Hi PGC, in some cases 2.0 is just exposing the bad things that you could do in 1.1 that weren’t handled well. For instance, in 1.1 exceptions on non-UI threads were not handled particularly well, but that behavior was changed in 2.0. In your case, due to the particular setting that you are changing to fix/hide the issue, you may have code in a worker thread that is directly using a UI object, which is definitely off-limits. You must Invoke() back to the UI thread from the worker thread before touching any UI objects. Just a guess, but a common mistake.

When you are actually running the 1.1 app (upgraded to 2.0) in the VS 2005/08 debugger, the new Managed Debugging Assistants (Debug/Exceptions…) can be helpful for finding subtle issues. In that same dialog, if you check “Thrown” for some of the other exception types, you may find exceptions occurring where you didn’t see them before. One caution being that _some_ are actually being handled, but the debugger will let you see them before the handler takes over.

Thanks for reading, Tom

By: PGC

PGC — Fri, 14 Dec 2007 08:09:42 +0000

Yes, the problem only came up when the app was run on the 2.0 framework. On 1.1, it works fine. I guess I have to check with the customer if they’re willing to have 1.1 installed on their machine as well.

That’s right, setting CheckForIllegalCrossThreadCalls to False was just a workaround, as we were just trying to convert our objects to version 2.0 then. It seems like making v1.1 apps run on v2.0 is a hit-or-miss thing and it’s hard to pinpoint the errors, but are there things that I have to particularly look out for just to get me started on identifying the error?

Thanks for the prompt response! The help is really appreciated.

By: Thomas

Thomas — Thu, 13 Dec 2007 15:58:03 +0000

PGC, I can’t tell if you have identified that the issue goes away if the 1.1 app is actually running on 1.1 Framework vs. 2.0, but there is no _technical_ reason that 1.1 can’t be installed on the Windows 2003 Server. They may not want to, which is a different issue. You would just install Framework 1.1 and then put a .exe.config next to your app to force it to use 1.1.

Given what you termed as a fix on the 2.0 version of the app, I would suggest that you are likely only suppressing the error by disabling CheckForIllegalCrossThreadCalls. Threading issues are extremely hard to track down, so you might consider spending some more time trying to diagnose the core issue.

Aside from forcing the app to run on 1.1 (if that matters) or modifying the code and redeploying, I do not think there is any way to actually fix the issue. You could try workarounds like starting the app with a Scheduled Task and giving it a timeout, so it can kill the process automatically after X hours, minutes.

Thanks for reading, Tom

By: PGC

PGC — Thu, 13 Dec 2007 07:04:14 +0000

Hi, I have a VB.NET program (built on v1.1) that is running on a Windows 2003 server. This machine has just the .Net Framework v2.0 installed (no v1.1).

The customer reported that the program works fine, save for one problem: after completing execution, the window stays opened, instead of automatically closing.

I’ve encountered this problem before, and I was able to fix it when I converted the program to v2.0 and set the value of the CheckForIllegalCrossThreadCalls property to FALSE (apparently, the program, being built on v1.1, is not thread-safe).

However, I do not see the converted version of the program being deployed to the client any time soon, so I was wondering if you could provide any pointers as to how to fix the error while sticking with running it (v1.1) on a v2.0 machine.

I apologize for the somewhat vague description of the problem, as I am not able to debug the program at the client’s machine.

Thanks.

By: Thomas

Thomas — Wed, 12 Dec 2007 18:45:32 +0000

classic_craig, I do not recommend mixing 1.1 and 2.0 applications in a folder/subfolder tree. The web.configs can interact with each other in very frustrating ways. I’ve spent many a frustrating hour trying to make such structures work. So, that isn’t to say that it isn’t possible, but expect to do a lot of testing.