Caelan

This is supported in [my fork](https://github.com/clowd/Clowd.Squirrel) which is active and has lots of fixes. The `--signTemplate` argument is what you need, eg `--signTemplate "yourCustomSignTool.exe sign {{file}} /options"`.

A hook failing to run will not break Squirrel, technically, but inside the hook is usually where the start menu and uninstall entry get created. `GitHubDesktop.exe` would be the process...

The issue with generating shortcuts for console apps is fixed in version 2.9.5 of [my fork here](https://github.com/clowd/Clowd.Squirrel).

Squirrel keeps the current version, and one previous version. It will clean up versions during every update. The reason `app-1.0.0` remains is probably because there was a running process in...

> Custom events won't fire in .NET 5, neither in .NET 6: the App does not detect Squirrel Aware Assembly Attribute as well. This is fixed in the fork here...

@mungojam FYI [my fork](https://github.com/clowd/Clowd.Squirrel) has removed the dependency on mono.cecil and now has several other ways of detecting a binary as squirrel aware that are friendly to net framework, dotnet...

This has been fixed (along with several other signing related issues) [in my fork here](https://github.com/clowd/Clowd.Squirrel).

This library supports installing the Full .Net Framework (up to .Net 4.8) with your application, but does not support dotnet core or .NET 5. You can choose which version of...

It looks like the logic for generating this path is here https://referencesource.microsoft.com/#System.Configuration/System/Configuration/ClientConfigPaths.cs,343 - and it will use a SHA1 hash of the strong name if your assembly has one, and...

You could try this: - Drop the stub you just compiled (and you say worked) into the same directory as Squirrel.exe and do a `--releasify`. Squirrel will use the one...