This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- MSXML3 included implicitly?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 08, 2011
10:01 AM
MSXML3 included implicitly?
Hi all!
While searching for the root cause of an installation issue (one setup affecting another and causing an auto-repair although there souldn't be any overlap) I recognized, that my Basic-MSI setup contains and installs the following files
- msxml3.dll.C8C0673E_50E5_4AC4_817B_C0E4C4466990
- msxml3a.dll.C8C0673E_50E5_4AC4_817B_C0E4C4466990
- msxml3r.dll.C8C0673E_50E5_4AC4_817B_C0E4C4466990
although neither these files nor any merge modules are included explicitly. Even when doing a text search on the tables of my IS project I am unable to find any hint for these files.
Could anybody explain where these files come from?
Thanks in advance
HazleNut
While searching for the root cause of an installation issue (one setup affecting another and causing an auto-repair although there souldn't be any overlap) I recognized, that my Basic-MSI setup contains and installs the following files
- msxml3.dll.C8C0673E_50E5_4AC4_817B_C0E4C4466990
- msxml3a.dll.C8C0673E_50E5_4AC4_817B_C0E4C4466990
- msxml3r.dll.C8C0673E_50E5_4AC4_817B_C0E4C4466990
although neither these files nor any merge modules are included explicitly. Even when doing a text search on the tables of my IS project I am unable to find any hint for these files.
Could anybody explain where these files come from?
Thanks in advance
HazleNut
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 08, 2011
01:14 PM
Hi again,
I found the reason. ".NET Scan at Build" had been enabled for several assemblies :rolleyes:
I found the reason. ".NET Scan at Build" had been enabled for several assemblies :rolleyes: