dotnet-installer/packaging/windows/clisdk/registrykeys.wxs

<?xml version="1.0"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
  <?include "Variables.wxi" ?>
  <Fragment>
    <ComponentGroup Id="AuthoredRegistryKeys">
      <Component Id="SetupRegistry_x86" Directory="TARGETDIR" Win64="no">
        <RegistryKey Root="HKLM" Key="SOFTWARE\dotnet\Setup\InstalledVersions\$(var.Platform)\sdk">
          <RegistryValue Action="write" Name="$(var.NugetVersion)" Type="integer" Value="1" KeyPath="yes"/>
        </RegistryKey>
      </Component>
      <Component Id="SetupRegistry_x86_RC2_Compat_Key" Directory="TARGETDIR" Win64="no">
        <RegistryKey Root="HKLM" Key="SOFTWARE\dotnet\Setup\InstalledVersions\$(var.Platform)\sdk">
          <RegistryValue Action="write" Name="1.0.0-rc4" Type="integer" Value="1" KeyPath="yes"/>
        </RegistryKey>
      </Component>
    </ComponentGroup>
  </Fragment>
</Wix>
Add missing wxs files for building MSI. 2015-11-17 20:53:49 -08:00			`<?xml version="1.0"?>`
			`<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">`
			`<?include "Variables.wxi" ?>`
			`<Fragment>`
			`<ComponentGroup Id="AuthoredRegistryKeys">`
Fix Component Rules violations. All resources should be installed by one and only one Component, where Component is defined by the Component/@Guid. The SetupRegistry_x64 and SetupRegistry_x86 Components were sharing the env vars across the 32-bit and 64-bit packages. That is a Component Rule violation. The fix is simple. Since the 32-bit registration is always required, let it handle the env var installation. The code is cleaner as well. 2016-01-26 22:25:52 -08:00			`<Component Id="SetupRegistry_x86" Directory="TARGETDIR" Win64="no">`
Setup the registry keys for CLI bundle detection. Fixes - #2588 2016-05-02 15:51:31 -07:00			`<RegistryKey Root="HKLM" Key="SOFTWARE\dotnet\Setup\InstalledVersions\$(var.Platform)\sdk">`
			`<RegistryValue Action="write" Name="$(var.NugetVersion)" Type="integer" Value="1" KeyPath="yes"/>`
x64 installer now creates registry keys in both x64 and Wow32 hives. This is required to enable 32-bit MSIs (like VS) that need to access the registry key on a 64-bit OS. Refer #250 2015-11-20 18:32:58 -08:00			`</RegistryKey>`
Change the install path, registry key path and environment component. Install path is now %ProgramFiles%\dotnet Registry root is now "HKLM\SOFTWARE\dotnet\Setup" Env variables setup is now associated with a versioned component - the registry keys. Environment resource cannot serve as a keypath hence it is coupled with a registry key which is the key path for the component. 2015-11-20 17:44:48 -08:00			`</Component>`
Setup RC2 registry keys for detection. Fixes - #2833 2016-05-03 16:11:32 -07:00			`<Component Id="SetupRegistry_x86_RC2_Compat_Key" Directory="TARGETDIR" Win64="no">`
			`<RegistryKey Root="HKLM" Key="SOFTWARE\dotnet\Setup\InstalledVersions\$(var.Platform)\sdk">`
Updating the branding on rel/1.0.0 to rc4. (#5267) 2017-01-12 13:14:57 -08:00			`<RegistryValue Action="write" Name="1.0.0-rc4" Type="integer" Value="1" KeyPath="yes"/>`
Setup RC2 registry keys for detection. Fixes - #2833 2016-05-03 16:11:32 -07:00			`</RegistryKey>`
			`</Component>`
Add missing wxs files for building MSI. 2015-11-17 20:53:49 -08:00			`</ComponentGroup>`
			`</Fragment>`
			`</Wix>`