dotnet-installer/packaging
John Beisner 6a0cf8d5e1
Changes in SDK bundle installation methodology (#121)
Changes in SDK bundle installation methodology:
1. Manage the 3 potential SDK bundle installation locations
In precedential order:
    A. the SDK bundle’s self-registered installation location [x64 or x86]
    B. ‘Program Files’ + “dotnet” [if 'dotnet.exe' exists]
    C. the “installpath’s” input parameter’s value
    D. ‘Program Files’ + “dotnet”
2. Communicate the SDK bundle installation location to the chained MSIs
3. Disable the CLI SDK MSI from installing ‘stand-alone’
4. SDK bundle self-registers the installation location value.

Other:
* Adding a file search for 'dotnet.exe'; updates
* Changing the MSI blocking conditional.
* Changed: "AuthoredRegistryKeys" to : "AuthoredRegistryKeys_x86node"
* Managing the x86 and x64 install locations
* "DOTNETHOME" should not overridable; adding an explicit override for identical install paths: "DOTNETHOMESIMILARITYCHECKOVERRIDE"; adding comments.
2018-11-21 09:38:54 -08:00
..
deb Updating the deb package of the SDK to specify a version range for the runtime and asp.net dependencies. 2018-05-08 18:42:57 -07:00
osx/clisdk Remove mac mark all 755 (#9177) 2018-05-01 12:33:13 -07:00
rpm Replace aspnetcore-store with the aspnetcore-runtime 2018-01-05 19:31:24 -08:00
windows Changes in SDK bundle installation methodology (#121) 2018-11-21 09:38:54 -08:00