-
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
Shortcut "Start in" property points to incorrect path after update #1805
Comments
No one helped, so I eventually figured out a work around. Maybe this will help someone else. I placed this code after the App loaded. The AppNumber is a string that represents the Squirrel app version folder (i.e. app-1.0.0)
Helper Code to update the shortcuts correctly, which also sets Run As Administrator in the Advanced tab.
|
I ran into something similar but my "Start in:" is completely garbled: It should be: I am using Electron Forge and their Squirrel.Windows maker. |
Squirrel version(s)
2.0.1
Description
I discovered this issue after many updates successfully pushed to users.
After pushing an update, some users need to set "Run AS administrator" in the Desktop icon Properties/Compatibility tab.
If the compatibility Tab is selected, the following message appears:
Upon investigation, I noticed that the Desktop icon "Start In" property points to the initial build number folder.
Example: Initial build folder is "app-1.0.0", and current (i.e. the last update pushed) build folder is "app-1.1.1".
Why is the "Start in" property pointing to the initial build folder (which no longer exists)?
Steps to recreate
Expected behavior
The desktop icon Property "Start in" is updated when Squirrel updates the app.
Actual behavior
App starts just fine, but if a user must select "Run as Administrator" in the Compatibility tab, they are presented with the error.
Additional information
My App is setup per Documentation, is SquirrelAware, and the only thing I can think off is I change the the name of setup.exe to MyApp.exe. However, this is the name of the file since initial install.
Any help is greatly appreciated.
The text was updated successfully, but these errors were encountered: