velopack/docs/4-FAQ.md

Squirrel.Windows

4 FAQ

Frequently Asked Questions for Squirrel.Windows, organized by area below.

Integrating

1. Can Squirrel.Windows be used on applications that aren't made with .Net?
   Yes, you can package a non-c# application in the same manner as described in the Getting Started guide. For additional customization, see section 2.1 on integrating custom squirrel events for non-c# apps.
2. How do I migrate a ClickOnce app to Squirrel?
   You may want to look into the ClickOnceToSquirrelMigrator migration helper.

Packaging

1. How can I tell was is going wrong with the releasify?
   Check packages\Squirrel.Windows.VERSION\tools\SquirrelSetup.log for logging information when creating packages.
2. Do I really have to add all the Squirrel DLLs to my app ? Yes, you have to add them all to the NuGet package, however, others have used ILMerge to generate a single assembly.

Distributing

1. Can I distribute update files on IIS?
   Yes you can, see 2.3 Distributing: Microsoft IIS for details.

Installing

1. The Initial Install via Setup.exe is failing. How do I learn what is going wrong?
   Check %LocalAppData%\SquirrelTemp\SquirrelSetup.log for logs related to the initial install.
2. Installer application doesn't do anything. The animation flashes but the application never starts.
   The app is likely crashing on the first run (see 2.1 Integrating: Debugging for details).
3. The Installer seems to be blocked in Enterprise environments. How can confirm this?
   Squirrel may be prevented from installing if Group Policy disallows the running of executables from %LocalAppData%. In this case, the "show log" button on the "installation failed" dialog will fail because Update.exe can not run to create a log file.

The Setup.exe for your application should still copy files to %LocalAppData%\SquirrelTemp as a pre-installation step. To verify that Group Policy is restricting you, execute Update.exe from the command line:

C:\>%LocalAppData\MyApp\Update.exe
This program is blocked by group policy. For more information, contact your system administrator.

The best course of action is to request that executables for Squirrel and your application be whitelisted by your corporate overlords.

Updating

1. How do I determine what is going wrong with the UpdateManager in MyApp?
   You can setup your \bin directory so you can execute MyApp in the Visual Studio debugger and simply step through the update process as well as catch exceptions and log the results (see 2.1 Integrating: Debugging for details)
2. I've Distributed a Broken Copy of Update.exe. How can I fix this?
   Sometimes, you might ship a broken copy of Update.exe that succeeds the initial install, but doesn't do what you want for some reason. To fix this, you can force an update of the Update.exe by including a copy of Squirrel.exe in your app update package. If Squirrel sees this, it will copy in this latest version to the local app installation.

---

Return: Squirrel.Windows