Doesn't check for computer configuration, to see if there is the right .NET inveroment

[nimcnaan]

installation doesn't check for computer configuration, to see if there is the right .NET inveroment, on windows server 2003

[jbirch]

Are you saying that it doesn't detect that .Net 2.0 is installed during the installer process, or that it doesn't configure the web applications to run under 2.0 when integrating with IIS, or something different? What are the symptoms you're seeing?

[jbirch]

I just ran a test and got this result:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -s W3SVC/1/ROOT/mapguide
Start registering ASP.NET scriptmap (2.0.50727) recursively at W3SVC/1/ROOT/mapguide.
The error indicates that this version of ASP.NET must first be registered on the  machine.

This is because on this image I installed IIS after !DotNet20. ASP.Net was showing in the registry as being registered, but the IIS install had walked on top of it.

To fix this, I ran the following;

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -ir
Start installing ASP.NET (2.0.50727) without registering the scriptmap.
........................
Finished installing ASP.NET (2.0.50727) without registering the scriptmap.

This worked fine; after I ran it I was able to manually assign the mapguide VDir the appropriate DotNet version. However, I'm not entirely convinced that we should do this as part of the installer.

[jbirch]

This step has been integrated into the IIS 5 and IIS6 install paths when the .Net setup is chosen as the default.