-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Build break: Shorten Windows targeting pack CAB name #29605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5,7 +5,13 @@ | |
| <Package InstallerVersion="$(var.InstallerVersion)" Compressed="yes" InstallScope="perMachine" /> | ||
|
|
||
| <MajorUpgrade DowngradeErrorMessage="A newer version of [ProductName] is already installed." Schedule="afterInstallFinalize" /> | ||
| <Media Id="1" Cabinet="$(var.Cabinet)" CompressionLevel="high" EmbedCab="$(var.EmbedCab)" /> | ||
|
|
||
| <?if $(var.EmbedCab)=yes?> | ||
| <!-- Ignore var.Cabinet This element should choose an appropriate name for the embedded CAB. --> | ||
| <MediaTemplate CompressionLevel="high" EmbedCab="yes" /> | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is an There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, the MediaTemplate is just a convenience element in the toolset that defers some of the mundane tasks to the compiler/linker when generating the table. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you think ASP.NET would move back to external cabinets? If not, you can likely just use the MediaTemplate. The downside is that with external cabinets and the template and multiple MSIs is that they can't exist in the same folder (becuase the cabs are just numerically named and will clash). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I doubt it but prefer to leave the option available without needing additional work to avoid those clashes. |
||
| <?else?> | ||
| <Media Id="1" Cabinet="$(var.Cabinet)" CompressionLevel="high" EmbedCab="no" /> | ||
| <?endif?> | ||
|
|
||
| <WixVariable Id="WixUILicenseRtf" Value="$(var.files)\eula.rtf" /> | ||
| <UIRef Id="WixUI_Minimal" /> | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just defence-in-depth. Nothing should depend in the CAB name whether it's embedded or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Side note: This will affect the runtime pack as well. I don't see a problem there but want to call it out.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be fine until the cab is made external again, mostly because of the shared wixlib we produce to share the MSI between multiple installers