I'm having awful trouble now that I've involved the reference "Microsoft XML, Version ..." into my project.
When I go to package it, it complains that there are no dependencies. However, it seems that
msxml.dll, msxmla.dll, msxmlr.dll
or
msxml2.dll, msxml2a.dll, msxml2r.dll
or
msxml3.dll, msxml3a.dll, msxml3r.dll
should be grouped together.
So if I package all these files, the xml-dlls refuse to register themselves. I removed the ($DLLSelfRegister) from the file setup.lst, and a manual register doesn't work either. A manual register requires an extra .BAT file for deployment.
Why would anyone use these ActiveX controls if they are exclusive to the developer's machine?
When I go to package it, it complains that there are no dependencies. However, it seems that
msxml.dll, msxmla.dll, msxmlr.dll
or
msxml2.dll, msxml2a.dll, msxml2r.dll
or
msxml3.dll, msxml3a.dll, msxml3r.dll
should be grouped together.
So if I package all these files, the xml-dlls refuse to register themselves. I removed the ($DLLSelfRegister) from the file setup.lst, and a manual register doesn't work either. A manual register requires an extra .BAT file for deployment.
Why would anyone use these ActiveX controls if they are exclusive to the developer's machine?