0

I have one add-in project that uses a WIX tool to create an installer. Previously, I was making '.exe' which was running fine.

But now requirement is changed due to security concerns. Now I want to create '.msi' file.

WIX gives me '.msi' successfully at 'C:/Path/To/MSI/addin.msi'.

But when I try to install the add-in by double-clicking on it, It's giving me an error :

enter image description here

When I try to hit command 'C:/Path/To/MSI/addin.msi' in CMD with administrator privileges, It works fine.

After Sometimes, I have found that created msi doesn't having revision number in properties.

enter image description here

Don't know how to add it & What value should come in this.

Smit Rathod
  • 101
  • 6

2 Answers2

2

Bootstrapper projects produce bundle .exes. They cannot produce .msi packages. If you must deliver only one .msi, you'll need to combine the MsiPackages in your bundle into one.

Bob Arnson
  • 21,377
  • 2
  • 40
  • 47
1

Seems like setting elevated privilege, scope + admin image can be helpful for you. Better to set all of them as shown, but if you have some restrictions about scope or so, just try different combinations.

 <Package InstallPrivileges="elevated" AdminImage="yes" InstallScope="perMachine">
ba-a-aton
  • 574
  • 1
  • 4
  • 14
  • Thanks. But can i achieve this in bootstrapper project? – Smit Rathod Jan 27 '23 at 14:17
  • seems like yes - https://stackoverflow.com/questions/26613030/wix-burn-bootstrapper-not-asking-for-admin-rights-for-my-msi. If you'll pack your msi with that properties to bootstrapper it will work – ba-a-aton Jan 27 '23 at 14:24