-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When Assembly name has spaces shortcuts wont work #713
Comments
Tested this and same issue, checked around and noted that this has been reported and reported fixed a few times but it still seems to be an issue and is easy to repeat.
Attempted to change application to 'SquirrelAwareVersion' and manually call events and CreateShortcutForThisExe's but effect was the same. Calling the CreateShortcutsForExecutable with an override exe reference produces the same and attempting to add in 'quotation' marks to the function call results in no creation of shortcuts. The only real solution at the moment appears to be changing your assembly name to remove spaces. |
Consider the PR #1401 that attempts to fix this issue. |
Consider also the possible back and forth with %20 in #1141 |
If I have a space in my Assembly name (I.E.: Hello World) then my applications executable will be
Hello World.exe
When the startmenu shortcuts are created the Taget at that time will be something like:C:\PathToApplication\Update.exe --processStart Hello World.exe
This will give the following exception while trying to start the application from the startmenu
This can be fixed by putting puting qoutes around the executables name in the Target of the shortcut
C:\PathToApplication\Update.exe --processStart "Hello World.exe"
. Maybe this can be fixed?The text was updated successfully, but these errors were encountered: