Programmatically determine who was installed first - IIS or .NET

[PetersonMike]

One gets countless hits when searching for discussions on the need to install
IIS before .NET so that ISAPI references are setup properly. It's also
documented that one can run apsnet_regiis.exe to correct the situation where
..NET is installed before IIS (as in a brand new installation of WinXP where
..NET is already loaded). My question is whether or not it is
programmatically possible to determine who was installed first (or last) from
a registry setting/configuration file entry/etc. I would rather not have all
of my installs (InstallShield) just automatically run aspnet_regiis but be
able to do some checking and present possible options to the user.

[Patrice]

It could have been fixed later, it could have been broken even if the
installation order is correct or the mapping could be correct but not use
the .NET framework version you need etc...

In short, it would be IMO better to check for the exact condition that
annoys you (that is an incorrect mapping) rather than for one particular
situation that could lead to this problem.
--

"PetersonMike" <Pe**********@discussions.microsoft.com> a écrit dans le
message de news: 92**********************************@microsoft.com...

One gets countless hits when searching for discussions on the need to
install
IIS before .NET so that ISAPI references are setup properly. It's also
documented that one can run apsnet_regiis.exe to correct the situation
where
.NET is installed before IIS (as in a brand new installation of WinXP
where
.NET is already loaded). My question is whether or not it is
programmatically possible to determine who was installed first (or last)
from
a registry setting/configuration file entry/etc. I would rather not have
all
of my installs (InstallShield) just automatically run aspnet_regiis but be
able to do some checking and present possible options to the user.