You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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?
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.
The text was updated successfully, but these errors were encountered: