Nov 16 2020
My WinForms app is using COM component and I am trying to make an installer for it.
It would provide a great benefit, because external library is using registry for settings and giving each app that using external SDK would be very nice.
The way I use the library is called Registration-Free COM Interop.
How it works:
1. I copy external DLL to my exe folder (usually in ExternalLib folder)
2. Copy .manifest for some of those files.
3. Create WinForms app without manifest (my real app)
4. Add custom manifest file from DLL manufacturer and rename it to MyApp.manifest.
5. Add dll to my project. VisualStudio will then create Interop.ExternalLib.dll and add it as reference,
And it works with WiX installer etc.
I've created and MSIX installer and it doesn't copy required files.
I can see using "files in package":
that manifests are not copied and nor the DLL folder.
The only file is copied is Interop file, and probably because it is referenced by the studio.
Is there any way to tell to MSIX: that folder and those files should always by included?
Lib will be updated etc, and there is literally no point to add lib files to the project because i never reference those directly, only via interop.
Jan 12 2021
Hi @Dmitri1285, have you taken a look at the following documentation: Prepare to package a desktop application (MSIX) - MSIX | Microsoft Docs There is a section called "Your application exposes COM objects...." Let us know if that is helpful.