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

Clickonce sign fail #73

Open
mybura opened this issue Aug 19, 2017 · 1 comment
Open

Clickonce sign fail #73

mybura opened this issue Aug 19, 2017 · 1 comment

Comments

@mybura
Copy link

mybura commented Aug 19, 2017

When running build with target Package, the resulting clickonce application manifest has the file size of the original settings.json file from the project. SC applies the transforms after Clickonce collected the file size and signs the manifest with the wrong file size. Workaround seems to be to do a Target=Rebuild and then a Target=Publish, Guess SC is invoked a bit late in the chain and "modifies" the resulting file after clickonce has created a manifest.

@aseminjakiw
Copy link

I have a similar problem. ClickOnce apparently hashes the *.exe.config file before SC transfroms it. So on application startup i get the a error that the hashes do not match. Any ideas?

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