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
- :
- Don't want to install system library files in my application folder
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
‎Jun 11, 2008
05:01 PM
Don't want to install system library files in my application folder
Hello,
I'm trying to create an install package for a .NET 3.5 application. InstallShield is pulling in and installing the system files from the .NET 3.5 framework (e.g. System.Core.dll, System.Runtime.Serialization.dll, System.Xml.Linq.dll, etc.) and putting them in my destination directory. In the build output I see a bunch of lines "Adding file '...' that is a dependency of component '...'") Is there any way to tell InstallShield not to do that?
Thanks,
Greg
I'm trying to create an install package for a .NET 3.5 application. InstallShield is pulling in and installing the system files from the .NET 3.5 framework (e.g. System.Core.dll, System.Runtime.Serialization.dll, System.Xml.Linq.dll, etc.) and putting them in my destination directory. In the build output I see a bunch of lines "Adding file '...' that is a dependency of component '...'") Is there any way to tell InstallShield not to do that?
Thanks,
Greg
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 11, 2008
05:08 PM
You can add these files to \Support\Filters.xml - see http://kb.acresso.com/doc/Helpnet/installshield15helplib/IHelpISXScannerFilterINIFormat.htm for more details.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 11, 2008
05:23 PM
As an aside, I can't reproduce this problem on IS2009. However, if I could, I suspect just setting .NET Scan at Build to "Properties Only" would solve the problem. Personally I dislike automated dependency scanners....
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 11, 2008
05:26 PM
That's expected - we updated the default list for IS2009. So that's an alternate answer - evaluate IS2009 and copy the updated Filters.xml, or otherwise get your hands on it.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 11, 2008
05:52 PM
Thanks, that worked; I just needed to make sure to make the filenames all lowercase.
- Greg
- Greg