So, I’ve got a single VB6 executable that references multiple VB6 COM DLLs. Is it possible for me to generate, on-the-fly, a manifest for the executable as well as a manifest for each of the referenced DLLs? If so, then how?
I would like to perform this operation as part of our build process without having to register the COM DLLs as part of the process.
NOTE: All the reg-free COM examples that I’ve found so far involve .NET interop, which is not a requirement for what I’m doing.
[EDIT]
After performing some preliminary testing using Unattended Make My Manifest, I’ve found that its just not as user-friendly as I would like. And, since there’s only a Sample.ini file for documentation I’ve had a pretty hard time understanding what should be put into that file compared to what doesn’t need to go into that file. Anyways, I’ve decided to craft manifests using my own tool. Hopefully, I’ll get permission from my employers to release the code as open source.
*For now, if you’re in the same position that I’m in and you would like to create a build and production environment that uses side-by-side/registration-free COM interactions, just know that its possible. I would recommend crafting them by hand with a simple DLL and consumer app at first, and then incrementally building on that until it suites your specific needs.**
We are using Unattended Make My Manifest in daily builds to create portable versions. It creates a single manifest that can be embedded to the executable with mt.exe