So, I have one VB6 executable that references several VB6 COM DLLs. Can I generate on-the-fly manifest for the executable file, as well as a manifest for each of the libraries referenced? If so, how?
I would like to perform this operation as part of our build process without having to register the COM-DLL as part of the process.
NOTE. All of the available COM versions of reg-free that I have found so far include .NET interoperability, which is not a requirement for what I'm doing.
[EDIT]
After preliminary testing with Unattended Make My Manifest, I found that it was just not as convenient as I would like. And, since there is only the Sample.ini file for documentation, it was rather difficult for me to understand what should be placed in this file compared to the fact that you do not need to enter this file. In any case, I decided to process the manifest using my own tool. I hope I get permission from my employers to release the code as an open source.
* At the moment, if you are in the same position that I am in and you want to create an assembly and production environment that uses parallel / registration-independent COM interactions, just know that this is possible, I would recommend them manually manually using a simple DLL and consumer application, and then gradually building it up until it satisfies your specific needs. **
source
share