Skip to content
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

Shorcut Target Is Wrong #920

Closed
leandroribeiro opened this issue Jan 8, 2017 · 8 comments
Closed

Shorcut Target Is Wrong #920

leandroribeiro opened this issue Jan 8, 2017 · 8 comments

Comments

@leandroribeiro
Copy link

Hey guys,

The shortcut target is wrong, instead of C:\Users\kbailey\AppData\Local\MyApp\Update.exe --processStart MyApp.exe is created C:\Users\kbailey\AppData\Local\MyApp\MyApp.exe.

Then this shortcut created doesnt works. =\

@aaababei
Copy link

This is intended. The behaviour was changed a while ago. More details in PR #868

@leandroribeiro
Copy link
Author

Right, but after this change the shortcut doesn't works and crash my application before run it.

My temporary fix was to get back to 1.4.4 version.

@gregsdennis
Copy link

I may be experiencing this as well. Please see my question on SO and see if you're experiencing the same thing.

@gregsdennis
Copy link

Confirmed that reverting to v1.4.4 fixed the issue.

@PushOrigin
Copy link
Contributor

Is there any resolution to this? I am migrating our app from 1.4.4 to 1.7.5 and when it updates the shortcut points to appname.exe in the root folder but the stub is never copied there. The appname_ExecutionStub.exe remains in the app-x.x.x directory. It appears that that is the only step that is missed. If I copy and rename the execution stub the shortcut works fine.

If I uninstall and install the new version it works fine so it only appears to be a problem on updates. Am I missing something on upgrading Squirrel beyond 1.4.4? Or am I looking at reinstalling on each desktop?

@PhilJenson
Copy link

Please see #1075 for a solution

@Thieum
Copy link
Contributor

Thieum commented May 7, 2019

@shiftkey duplicate of #1075 , which has more information than this issue. I would close this one in favor of #1075

@shiftkey
Copy link
Contributor

Closing this out in favour of #1075

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants