Skip to content
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

How to reference bundle identifier value in Wix fragment? #10491

Open
Sidders22 opened this issue Aug 5, 2024 · 2 comments
Open

How to reference bundle identifier value in Wix fragment? #10491

Sidders22 opened this issue Aug 5, 2024 · 2 comments

Comments

@Sidders22
Copy link

Sidders22 commented Aug 5, 2024

I want to customize the MSI installer with a Wix fragment, but I don't want to have to edit this file if I later decide to change the name of my app.

So with that in mind, is there a way to reference the full bundle identifier value in a Wix fragment without having to hardcode it, much like how "MyCompany" and "MyApplicationName" works?

Example:

<RegistryKey Root="HKCU" Key="Software\MyCompany\MyApplicationName" Action="createAndRemoveOnUninstall">
     <RegistryValue Name="AppDataFolder" Type="string" Value="[AppDataFolder]com.bundleidentifier.app" />
</RegistryKey>
@FabianLars
Copy link
Member

Tauri currently does not run the template engine on fragments so you can't use {{bundle_id}} the same as in main.wxs.

I don't know if there's a way to forward variables to fragments, or have global wix variables but i think it'd be nice if fragments would be (optionally?) interpreted as a template.

@Sidders22
Copy link
Author

That's a shame, but thank you for the quick response. It would be great if variables could somehow be forwarded to fragments so the files can be used as a template, instead of needing to hardcode values.

I did try doing 'Value="[AppDataFolder]com.MyCompany.app' as an experiment too, but no luck!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants