Forum Discussion
Signtool cannot sign msix file produced by dotnet publish
Used dotnet publish to generate a msix package (from Blazor MAUI project). During the process, dotnet has signed the msix file using our EV certificate, but it did not time-stamp it. So we’ve decided...
Additional thought (for anyone running into a signing issue in general, but not necessarily the issue reported here)
Please note that he signtool command requires elevation. In the example above, the Q: drive must be available after elevation for this to succeed. Sometimes we copy the package locally, then sign and copy back as a work-around.