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
- :
- Workaround
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
Jan 24, 2018
03:49 AM
migration from ISWiAuto22 to ISWiAuto24 (Installshield 2018)
Hello all,
i have upgraded my ism files from 2015 to 2018 and i figured out, that my "headless" vbs script now crash. Using the same Script with 2015 (ISWiAuto22 ) everything was fine.
After some trial and error i figured out, that if i am using Newtonsoft.Json.dll in my MergeModule.ism file the build crash on the commandline. If i do the same stuff in the IDE, the build is running without error.
At the commandline the build crashed after "Building File table".
I have attached a sample project which crashes if i'm using 2018. Using in 2015 everything is fine.
Any Idea?
================= Logging started at 1/24/2018 10:41:44 ==================
Created release folders
Directory table successfully built
Component table successfully built
Loading File table
Building File table
i have upgraded my ism files from 2015 to 2018 and i figured out, that my "headless" vbs script now crash. Using the same Script with 2015 (ISWiAuto22 ) everything was fine.
After some trial and error i figured out, that if i am using Newtonsoft.Json.dll in my MergeModule.ism file the build crash on the commandline. If i do the same stuff in the IDE, the build is running without error.
At the commandline the build crashed after "Building File table".
I have attached a sample project which crashes if i'm using 2018. Using in 2015 everything is fine.
Any Idea?
================= Logging started at 1/24/2018 10:41:44 ==================
Created release folders
Directory table successfully built
Component table successfully built
Loading File table
Building File table
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 25, 2018
12:46 AM
Flexera found a workaround...
The issue appears to be related to the component .Net settings, specifically the '.NET Scan at Build' setting. In the project you have this set to 'Dependencies and Properties'.
To work-around this issue for the time-being you can change this setting to 'Properties Only' or 'None' which should allow the automated builds to complete without error.