I have some specific questions about signed MSIX deployment through the Windows 11 Store, that I've not been able to find answers to.
I have a 64-bit C++ application (WIN32), deployed and sold through the Microsoft Windows 10 Store using the UWP adaptor layer from Microsoft.
I want to deploy this in the Windows 11 Store, but additionally with:
- the ability to load 3rd party DLLs (specifically: audio plug-ins in VST3 format) from an industry-standard folder
- the ability, at time of installation, to additionally deploy a signed VST3 plugin (again, this is a DLL) to a industry-standard folder
By way of experimentation, I can easily create a .MSI file that deploys non-signed version of the EXE (without the UWP adaptor) and my VST3 DLL where I want them. This EXE can load-up 3rd-party VST3 DLLs as expected, and my VST3 DLL can be loaded by other audio authoring tools.
I can see how to convert the .MSI file into a .MSIX file.
However, I've not found out how to create a .MSIX file that is compatible with Windows 11 Store Deployment
My three questions are:
1) I am not at all clear how I would get a certificate that will sign my application. For my current UWP-adapted C++ .EXE, this signing is handled automatically through Windows Visual Studio 2019. Will this still be the case for my .MSIX file?
2) I am not at all clear that what I want - deploying both a signed .EXE and signed .DLL - will be supported for paid, auto-updating Windows 11 Store applications. Is this supported? And if not, why not?!
3) Assuming the above works - am I correct in assuming that I'll be able to sell my application (EXE, VST3 DLL) to Windows 10 Users via an updated Windows 10 Store?