Question about installing .net 2.0 when .net 1.1 is present (HELP)

[jkudrle]

Hi,

I have several machines with .net 1.1 installed. On these machines are
a few MMC plugins that have been developed with Visual Studio 2003
(.net 1.1).

I have noticed that if .net 2.0 is installed on these machines that the
MMC plugins developed with .net 1.1 no longer work (repeated errors
about snapins failing to initialize).
This happens when opening the MMC console and selecting the "Add/Remove
snap-in" option. If I select any snapin that was developed with 1.1,
this problem appears.
Consequently, the .NET Framework 1.1 configuration snapin also exhibits
this issue.

Strangely, if I uninstall .net 2.0, all of the .net 1.1 MMC plugins
begin to work again (including the .NET Framework 1.1 configuration
plugin.

Does anyone know why this is happening and if so, what is the proper
mechanism for getting these snapins to work when .net 2.0 is installed.


Thanks,

-john

 

[Phil Wilson]

I think you'll find what's happening is that MMC is loading the default
runtime, and that's the highest one on the system, and your 1.1 snapins
don't work in 2.0. Something like process explorer would confirm that or
not. The problem with this idea is that I wouldn't expect the 1.1 framework
config tool to fail, unless in a 2.0 environment you're supposed to run the
2.0 tool for all assemblies.

 

[jkudrle]

Thanks for this information. I believe I misspoke a little about the
..net 1.1 configuration tool. If I access this via the Administrator
Tools->Microsoft .NET Framework 1.1 Configuration; then the snapin
properly loads.
However, if I simply open the MMC console and select Add/Remove Snapin
and select the .NET Framework 1.1 configuration snapin; this scenario
produces the failure.
This would seem to coincide that the MMC does load the default runtime
while launching the tool from the Administrator Tools section loads the
proper (1.1) runtime.

Is it safe to say that MMC snapins built with the 1.1 runtime must be
rebuilt as to utilize the 2.0 runtime (assuming that the MMC is
loading the 2.0 runtime by default).

Thanks,

-john

I think you'll find what's happening is that MMC is loading the default
runtime, and that's the highest one on the system, and your 1.1 snapins
don't work in 2.0. Something like process explorer would confirm that or
not. The problem with this idea is that I wouldn't expect the 1.1 framework
config tool to fail, unless in a 2.0 environment you're supposed to run the
2.0 tool for all assemblies.
--
Phil Wilson
[Microsoft MVP-Windows Installer]

Hi,

I have several machines with .net 1.1 installed. On these machines are
a few MMC plugins that have been developed with Visual Studio 2003
(.net 1.1).

I have noticed that if .net 2.0 is installed on these machines that the
MMC plugins developed with .net 1.1 no longer work (repeated errors
about snapins failing to initialize).
This happens when opening the MMC console and selecting the "Add/Remove
snap-in" option. If I select any snapin that was developed with 1.1,
this problem appears.
Consequently, the .NET Framework 1.1 configuration snapin also exhibits
this issue.

Strangely, if I uninstall .net 2.0, all of the .net 1.1 MMC plugins
begin to work again (including the .NET Framework 1.1 configuration
plugin.

Does anyone know why this is happening and if so, what is the proper
mechanism for getting these snapins to work when .net 2.0 is installed.


Thanks,

-john