mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions
dotnet-installer/packaging/osx/sharedframework/shared-framework-distribution-template.xml

25 lines
1.2 KiB
XML
Raw Normal View History

Fill out pkg installer targets This causes three pkg files to be produced: * A component pkg for the shared framework. * A component pkg for the shared host. * A product archive which includes the above two components. The product archive also needs a distribution.xml file which contains metadata about the package (name, title, images, etc.). The installer for the "SDK" itself is still using logic implemented in package-osx.sh. We should move this logic into the build target as well, but we may want to wait until the CLI is using the shared framework to do so.
2016-03-09 13:26:37 -08:00
<?xml version="1.0" encoding="utf-8" standalone="no"?>
<installer-gui-script minSpecVersion="1">
Cleanup OSX installer to have same title as windows installer.
2016-05-04 17:38:25 -07:00
<title>{SharedFxBrandName} (x64)</title>
Fill out pkg installer targets This causes three pkg files to be produced: * A component pkg for the shared framework. * A component pkg for the shared host. * A product archive which includes the above two components. The product archive also needs a distribution.xml file which contains metadata about the package (name, title, images, etc.). The installer for the "SDK" itself is still using logic implemented in package-osx.sh. We should move this logic into the build target as well, but we may want to wait until the CLI is using the shared framework to do so.
2016-03-09 13:26:37 -08:00
<license file="eula.rtf" mime-type="application/rtf" />
<background file="dotnetbackground.png" mime-type="image/png"/>
<options customize="never" require-scripts="false" />
<volume-check>
<allowed-os-version>
<os-version min="10.10" />
</allowed-os-version>
</volume-check>
<choices-outline>
Fix OSx Pkg installers - Make the .Net CLI SDK install SxS. - Make the .Net Host upgrade till RTM(v.1.0.0). - Make the .Net Core Sharedfx pkg to use the SharedFx Nuget version instead CLI version.
2016-03-25 14:46:04 -07:00
<line choice="{SharedFxComponentId}.pkg" />
<line choice="{SharedHostComponentId}.pkg" />
Fill out pkg installer targets This causes three pkg files to be produced: * A component pkg for the shared framework. * A component pkg for the shared host. * A product archive which includes the above two components. The product archive also needs a distribution.xml file which contains metadata about the package (name, title, images, etc.). The installer for the "SDK" itself is still using logic implemented in package-osx.sh. We should move this logic into the build target as well, but we may want to wait until the CLI is using the shared framework to do so.
2016-03-09 13:26:37 -08:00
</choices-outline>
Update OSX branding. And also address PR feedback.
2016-04-27 17:20:52 -07:00
<choice id="{SharedFxComponentId}.pkg" visible="true" title="{SharedFxBrandName} (x64)" description="The .NET Core Shared Framework">
Fix OSx Pkg installers - Make the .Net CLI SDK install SxS. - Make the .Net Host upgrade till RTM(v.1.0.0). - Make the .Net Core Sharedfx pkg to use the SharedFx Nuget version instead CLI version.
2016-03-25 14:46:04 -07:00
<pkg-ref id="{SharedFxComponentId}.pkg" />
Fill out pkg installer targets This causes three pkg files to be produced: * A component pkg for the shared framework. * A component pkg for the shared host. * A product archive which includes the above two components. The product archive also needs a distribution.xml file which contains metadata about the package (name, title, images, etc.). The installer for the "SDK" itself is still using logic implemented in package-osx.sh. We should move this logic into the build target as well, but we may want to wait until the CLI is using the shared framework to do so.
2016-03-09 13:26:37 -08:00
</choice>
Update OSX branding. And also address PR feedback.
2016-04-27 17:20:52 -07:00
<choice id="{SharedHostComponentId}.pkg" visible="true" title="{SharedHostBrandName} (x64)" description="The .NET Core Shared Host." >
Fix OSx Pkg installers - Make the .Net CLI SDK install SxS. - Make the .Net Host upgrade till RTM(v.1.0.0). - Make the .Net Core Sharedfx pkg to use the SharedFx Nuget version instead CLI version.
2016-03-25 14:46:04 -07:00
<pkg-ref id="{SharedHostComponentId}.pkg" />
Fill out pkg installer targets This causes three pkg files to be produced: * A component pkg for the shared framework. * A component pkg for the shared host. * A product archive which includes the above two components. The product archive also needs a distribution.xml file which contains metadata about the package (name, title, images, etc.). The installer for the "SDK" itself is still using logic implemented in package-osx.sh. We should move this logic into the build target as well, but we may want to wait until the CLI is using the shared framework to do so.
2016-03-09 13:26:37 -08:00
</choice>
Fix OSx Pkg installers - Make the .Net CLI SDK install SxS. - Make the .Net Host upgrade till RTM(v.1.0.0). - Make the .Net Core Sharedfx pkg to use the SharedFx Nuget version instead CLI version.
2016-03-25 14:46:04 -07:00
<pkg-ref id="{SharedFxComponentId}.pkg">{SharedFxComponentId}.pkg</pkg-ref>
<pkg-ref id="{SharedHostComponentId}.pkg">{SharedHostComponentId}.pkg</pkg-ref>
Fill out pkg installer targets This causes three pkg files to be produced: * A component pkg for the shared framework. * A component pkg for the shared host. * A product archive which includes the above two components. The product archive also needs a distribution.xml file which contains metadata about the package (name, title, images, etc.). The installer for the "SDK" itself is still using logic implemented in package-osx.sh. We should move this logic into the build target as well, but we may want to wait until the CLI is using the shared framework to do so.
2016-03-09 13:26:37 -08:00
</installer-gui-script>
Reference in a new issue Copy permalink