.Net version

[nomad]

Ally...was just about to buy the UK mirror combo when I noticed it requires .Net 1.1

I know with IIS, you can switch between 1.1, 2.0 or 3.0 as you feel like per pool, but as this is for my girlfriend and she has .Net 2 on XP home, I need to check the following...

You tried running 2.0 and 1.1 side by side on a XP box?
Did this cause any issues for the mirror s/w or the box itself?

regards & TIA

[cyberblob]

Ally...was just about to buy the UK mirror combo when I noticed it requires .Net 1.1

I know with IIS, you can switch between 1.1, 2.0 or 3.0 as you feel like per pool, but as this is for my girlfriend and she has .Net 2 on XP home, I need to check the following...

You tried running 2.0 and 1.1 side by side on a XP box?
Did this cause any issues for the mirror s/w or the box itself?

regards & TIA

This does not matter. We have systems that have 1.0, 1.1, 2.0, 3.0 .NET installed on them. This was the way Microsoft designed it. If you don't have the necessary .NET runtime installed the .NET app will not run.

If an application needs 1.1 to run and you only have 2.0 installed. It will error on execute of the application. You must then go install .NET 1.1 and all service packs and security fixes.

The only time it will get to be a problem is if you install .NET 2.0 first, then go back and install .NET 1.1 on a server with IIS. This will mess up IIS's .NET settings. You then need to fix it by running a command line app in .NET 2.0 for resetting up IIS's .Net references.

[nomad]

This does not matter. We have systems that have 1.0, 1.1, 2.0, 3.0 .NET installed on them. This was the way Microsoft designed it. If you don't have the necessary .NET runtime installed the .NET app will not run.

If an application needs 1.1 to run and you only have 2.0 installed. It will error on execute of the application. You must then go install .NET 1.1 and all service packs and security fixes.

The only time it will get to be a problem is if you install .NET 2.0 first, then go back and install .NET 1.1 on a server with IIS. This will mess up IIS's .NET settings. You then need to fix it by running a command line app in .NET 2.0 for resetting up IIS's .Net references.

Thanks CB...was just concerned as it was the GF's PC and this was the thrust of my question. .Net 2 first and then installing .Net 1.1....what will happen? Thanks anyway, I'll toast an old laptop and try it on that first, but I'd have thought, that maybe Ally might have tried this.

I'd like to just spend the money on the product rather than having to investigate the issue for myself first. Whether it was an issue or a non issue was what I was trying to find out.

[cyberblob]

Installing 1.1 after 2.0 is not a problem as long as you are not running a server.

On a normal PC it will get registered in the registry correctly and will cause no issues.

[RacerX]

yeah, agreed.
i had net 1.1 on XP and installed 2.0.5 alongside to test it out just now, and everything seems fine, and the mirror updater works fine as well.