Issues with package -p zip #1881
-
The Windows app will run OK on the machine that compiles it, but when unzipped and run on another machine, this error is encountered:
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 10 replies
-
Thanks for the report. I haven't seen that one before; I'm guessing the MSI installer is setting whatever flags are required as part of the installation process. I can't say I know what the workaround for this is (other than the manual unblock that you've already found). I'm guessing the fix will be one of two things:
If you're able to find a programmatic change that makes this work, I'm happy to integrate it into Briefcase. |
Beta Was this translation helpful? Give feedback.
-
This looks like Windows' "mark of the web" "feature". This is a problem for the ZIP because the provenance of the DLLs is being tracked as the ZIP is moved from machine to machine while the MSI intentionally doesn't mark the DLLs as foreign. I was able to bypass both of these errors, though, by adding the content below to a file named <configuration>
<runtime>
<loadFromRemoteSources enabled="true"/>
</runtime>
</configuration> Alternatively, you can remove the mark of the web using the Unblock option in properties for all the DLLs included in the ZIP...but that'd have to be done each time the ZIP is extracted. |
Beta Was this translation helpful? Give feedback.
-
Maybe this is a dumb question: But when is the "Mark of the Web" added to the file? E.g. when I unpack the ZIP on the same computer where it was packed and copy this to a USB stick, would the exe then run (from the stick) on a different computer? And when I then copy the folder to the other computer? |
Beta Was this translation helpful? Give feedback.
Thanks for the report. I haven't seen that one before; I'm guessing the MSI installer is setting whatever flags are required as part of the installation process. I can't say I know what the workaround for this is (other than the manual unblock that you've already found).
I'm guessing the fix will be one of two things:
clr.AddReference()
to allow an "unsafe load" of the Python and WebKit binaries.If you're able to find a programmatic change that makes this work, I'm happy to integrate it into Briefcase.