-
Notifications
You must be signed in to change notification settings - Fork 39
Shortcuts not working with console app #61
Comments
Hi Mat, Squirrel has never worked with console apps and I've not taken the time to look at this since I created the fork. I believe the primary issue is that, because of #24 we need to use stubexecutables. (your shortcut points to a "stub" in the root application directory, instead of to the version binary in This is tracked in the upstream issues Squirrel#1491 and Squirrel#1098. I think that we should be able to support console apps, so I will leave this open as a feature request until I can look at it or someone else does. There are three possible approaches:
|
Thanks for the detailed reply. I v just used the |
If you are using |
I have published the pre-release 2.9.5-gdcbdbd. It simply removes the check preventing stub's being created for console apps. I tested this, and it seemed to work nearly perfectly. The stub is a GUI exe, but all it does is launch the console app in a new window and exit. The one downside is that if you run the stub from a console you'll see the console pop-up in a new window instead of the current console. When running shortcuts, or running the stub from windows explorer, it works as expected. This is good enough to close this issue until #24. |
Perfect. That will work fine for my usecase. Thanks. |
I v been trying to get Squirrel working with an internal tool that is just a console app. Everything seems correct during pack and install, after installation it runs as expected but the shortcuts dont work as the exe they link to doesnt exist. Looking at a WPF app I use Squirrel with there is a exe at the root of the installation folder that seems to be missing in this case.
I have created a test app that shows the issue. Any help on this issue would be appreciated.
See below log from pack command.
Installer log
The text was updated successfully, but these errors were encountered: