Simple question on Framework 1.0 to 1.1 conversion

  • Thread starter Thread starter Luc Bisson
  • Start date Start date
L

Luc Bisson

Hi all,

We are using Framework 1.0 for all our ASP.NET and Windows application
projects.

We plan on going to Framework 1.1.

On MSDN, they say that for Windows application, we have to add a section in
the configuration file so the application will be forced to use the 1.1
framework.

For an ASP.NET Application, on installing, the 1.1 Framwork, the ISAPI
filter will automatically change to the 1.1 filter at the root of IIS. So,
by default, the ASP.NET will use the new framework if not told different on
the web site level.

But what about a class library project or assemblies that are in the GAC?
Is there a way for those components to use the 1.1 framework and not having
them to be recompiled with VS 2003?

Since those components doesn't have a configuration file and are using a
strongly typed name is there a way to tell those components to use 1.1?

Thank's for any idea.
 
DLLs don't have configuration settings. They will run with whatever version
is loaded. So if you have an EXE and tell it to load the v1.X framework,
then all the assemblies it loads (from whereever) will load with that
Framework.

-mike
MVP
 
That mean's that even my DLL's registered in the GAC with strongly typed
name will in turn use the new framework even if they are strongly typed
named components? Even if their manifest tells to use a specific version of
an assembly within the old framework?

If that's work, part of my problem is resolved.

And what about components defined as NT services. Are they considered
windows applications? If so, are they going to use the new framwork if the
configuration file states to use the new one? And what about the assemblies
called by those services?

Thank's for the answer and hope to receive news soon.
 
DLLs are loaded into a process. Whatever framework that process is using is
the framework the DLLs will be loaded with. Basically, any EXE that is run
with a config redirecting it will load in that framework. The notable
exception is when you are being loaded by something other than directly
running an EXE, for instance, in ASP.NET.

-mike
MVP
 
Thank's for the answer. For ASP.NET, upon installing the new framework, a
new IIS filter is used to instruct the aspnet_wp.exe process to use the new
framework. The new filter is located at the exact location where the
framework was installed.
 
Back
Top