Problem: COM+ Exported MSI contains an unrelated dll
mrashi...@hotmail.com
to explain the scenario where I observed the problem.
1. On my production server, I have two different COM+ applications
running. Let's say the application names are ABC and DEF.
2. ABC COM+ application hosts, for example, components from COM dll's
A.dll, B.dll and C.dll.
3. DEF COM+ application hosts, for example, components from COM dll's
D.dll, E.dll and F.dll.
4. Some requirement caused an update of A.dll. The updated version of
A.dll was installed on a test server. After testing was finished, the
COM+ application ABC was exported from test server to create ABC.MSI.
5. We then tried to install ABC.MSI on the production server. It
prompted to overwrite existing files on the server. The strange thing
was that it also prompted to overwrite D.dll which was not part of ABC
COM+ application (neither on test nor production server).
6. Installation did work however this resulted in a newer version of
D.dll getting copied on production server causing problems there.
Following on from this, we exported ABC COM+ application from
production server and installed it on a 2nd test machine. This time it
did not prompt to overwrite D.dll. Installing it on the first test
machine and re-exporting didn't reproduce the problem either.
The question is that how does ABC.MSI exported in step 4 contained an
unrelated dll?
How does COM+ export picks up the list of files that it needs to
include in the MSI? Can this be specified/viewed by user?
Is there a difference between export using Component Services snap-in
and export using COMAdminCatalog object methods?
The development, test and production servers all run Windows 2000
server (SP4).