I have created a Bootstrapper with WiX 3.7.
Now, when I start it on a Windows7 machine, the UAC-Dialog will be shown before installing .NET 4.0 as a prerequisite. Thats ok. I am searching now for a way to "sign" the Installer/Bootstrapper, that I can set the product-name and the company-name for the UAC-Dialog. How can I do this?
There are signing tasks built into the wix.targets that will help you sign your Bundle. You can read about the in the Insignia topic in the WiX topic. The UAC will show the information from the certificate.
Related
I have a application that uses Wix for its installer.
I'd like to understand where the UAC window takes its app name from, I am having an old name where the UAC window appears does not correspond with current productname defined in Wix.
Digital Signature: It looks like your MSI is signed with a code-signing certificate?
"If you Authenticode-sign your .msi package, Windows will show that as the name. Otherwise, you get MSI's temporary copy of it, which has a random name." - source.
Signtool.exe: You need to modify your signtool.exe parameters:
Odd 'Program name' when installing signed msi installer
Some old answers with comments discussing signtool.exe parameters:
What is causing to show Publisher to unknown on UAC despite signing exe using signtool
Windows Installer Unknown Publisher
Links on Digital Signing:
Installshield Custom Dialogue Installer
How to add publisher in Installshield 2018
I am writing managed bootstrapper application and would like to make it work like Web-based installer (force it to download msi from webserver).
Where will product be downloaded by default? Why SourceFile is mandatory for download of package?
please share sample code.
Separating the concerns:
Managed bootstrapper application
Great. The standard application is very basic. The managed bootstrapper application for WiX itself shows how creative you can get.
Work like Web-based installer
From the following questions, it seems you know about the DownloadUrl attribute.
Where will product be downloaded by default?
It would be a special case to have to know this. The bootstrapper engine (burn) is a package manager and takes care of performing operations with the downloaded package.
Why SourceFile is mandatory for download of package?
SourceFile indicates the location on your build machine. WiX creates a checksum from it so burn can tell if the download is corrupted or different than what was planned.
I've developed a VSTO addin with VS2012 signed by a DigiCert certificate. I need to deploy it to all the Enterprise users so the installer shouldn't prompt the user because it will fail since all the installation process is silent.
I'm not able to do it since it always ask the user if it should or shouldn't install. If I set VSTOInstaller /S it doesn't install 'silently'.
Is there any way to do this?
Thanks on advanced.
I found the answer. To solve this you have to install the public key certificate in your installer:
certutil -addstore TRUSTEDPUBLISHER "yourcertificate.cer"
Then, you just use VSTOInstaller:
VSTOInstaller.exe /I "youraddin.vsto" /S
That's all folks!
Yes you can.
Just Uncheck the ClickOnce manifest CheckBox and Check the signing the assembly using any .snk file.
You will need to create installer project and the rebuild the installer project will provide you the .msi and .exe file you can execute the following command on command prompt(Administator).
Though rebuilding of installer project will automatically check the ClickOnce checkBox but you can ignore that.
Below is the link for creating Installer project for AddIn.
https://learn.microsoft.com/en-us/previous-versions/visualstudio/visual-studio-2010/ff937654(v=msdn.10)
Looks like you need to GPO for deploying the software (using MSI installers).
How to use Group Policy to remotely install software in Windows Server 2008 and in Windows Server 2003
How to use Windows Installer and Group Policy to deploy the VPModule.msi in an Active Directory domain
Installing Software Using GPO
Also see the Deploying an Office Solution section in MSDN.
I'm trying to certify a desktop application for Windows 8.1 using Windows App Certification Kit 3.1.
Everything is fine with the exception of the uninstall. I created the MSI file using Wix Toolkit 3.6. When the application installs it creates an entry in Programs and Features as well as a shortcut for uninstalling.
When I trigger the uninstall from either of these locations it works properly and all the files and registry entries get removed.
However, when the WACK launches the uninstall process, the MSI starts the installation process instead.
Is there a specific command from msiexec I need to test that WACK might be using to cause this?
I really do not understand why the Kit will launch the installer again.
Thank you,
Fernando
I found the problem and my solution.
The WACK calls the uninstall process using the Change option instead of Uninstall. You can test this by going to *Programs and Feature*s and clicking Change.
Since my application does not support changing or repairing, I simply set ARPNOREPAIR and ARPNOMODIFY to "Yes" and now WACK only calls uninstall.
The other option is to offer the Change/Repair dialog on your setup project and have the Remove check-mark available.
Hope this helps.
Cheers,
Fernando
Anyone have a WiX UI sequence for installing an ASP.Net Web site? Something that asks for a virtual dir, and app name similar to what the Visual Studio install projects do?
I've worked up an initial solution here.