Maybe someone can shed some light on the readme.htm file that Im completely not reading regarding the installations of a new version ASP.NET along side existing versions, which explains that magic flag to not automatically upgrade script maps.

The few machines that I have recently upgraded from 1.0 to 1.1 and even a few up to 1.2 (v2 bits) I have noticed that it does replace the script maps for all of the existing applications. (aspnet_regiis -i).  It would be nice to know of some flag that I can pass into the installation that PREVENTS this from happening.  Rolling out new builds is usually a good thing, until it breaks existing applications.

IMHO: The installation should NOT upgrade existing applications script maps at all.  The system admin should have to explicitly migrate these applications on their own with the aspnet_regiis tool (or even this cool tool). 

1 Comment

• Adam said Thursday, November 20, 2003 1:15:00 PM

  Run the setup exe from the command line like so:
  
  dotnetfx.exe /q:a /c:"install /noaspupgrade /l /q"
  
  This worked in V1.0 when upgrading to 1.1, so I assume this will work for future versions.