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

Application Executables gets incorrectly replaced with Stub Executable #938

Open
simquad opened this issue Jan 27, 2017 · 2 comments
Open

Comments

@simquad
Copy link

simquad commented Jan 27, 2017

Issue: Actual application EXE gets replaced with stub, if EXE found in app.publish*

Squirrel Version: 1.5.2

Background: Changing an application from being ClickOnce to Squirrel, and had left Enable ClickOnce Security Settings checked. As a result of this, an extra copy of the application EXE is placed in this directory.

When creating the releasify package, I can confirm the correct application EXE is in the package, in the correct position.

On doing an install however, attempting to then run the stub, crashes:
image

Attempting to run what I believe to be the application EXE from the app-x.y.z folder, does not work either.

Running BeyondCompare against both of the EXEs, I'm told they are identical.

It therefore would seem the application EXE is getting overwritten with the stub EXE on application install/update.

Related Issue: #868

* It may be for any EXE, but certainly was in my case.

@simquad simquad changed the title Executables get replaced with Stub Executable Application Executables gets incorrectly replaced with Stub Executable Jan 27, 2017
@simquad
Copy link
Author

simquad commented Jan 27, 2017

For those finding this issue, my fix was to disable "Enable ClickOnce Security Settings", which prevented the EXE being made in app.publish.

@ChrisPulman
Copy link

I have also experienced this issue however the "ClickOnce Security Settings" were not enabled and never were. 1.4.4 did not have this issue and was introduced as of 1.5.1. The install only included one exe

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

2 participants