|
|
Rank: Member
Groups: Member
Joined: 6/1/2015
Posts: 16
|
Installshield wants to add this dependency for the EO dll's, but this dependency is not mentioned in the help files....
Is this correct, is this merge module required or not?
From installshield log...
Adding merge module 'Microsoft Data Access Components 2.7 (English)' that is a dependency of component 'EO.Base.dll'
Adding merge module 'Microsoft Data Access Components 2.7 (English)' that is a dependency of component 'EO.WebBrowser.dll'
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
No. I can confirm that our product does not have any dependency on those components.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/1/2015
Posts: 16
|
Thanks, very strange that Installshield insists on including them, this wasn't the case with the 2014 version builds.
Generally this means they are accidentally referenced in the VS project (even if not used).
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
We are not sure why either. EO.Base.dll explicitly references System.Data.dll, which is a part of .NET frameworks. That might be what triggered it. However referencing System.Data.dll does not mean we use Microsoft Data Access Components. EO.WebBrowser 2014 references System.Data.dll as well.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/1/2015
Posts: 16
|
For anyone else stuck with this issue in Installshield the workaround is to right click over the EO .dll within the Installshield project and select 'Dependencies from scan at build...'. You can then manually exclude the MDAC that Installshield insists on adding.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Great. Thanks for sharing!
|
|