MsBuild works from VS2015 Cmd but gives licence error from VS2017 Cmd
works fine and has done for a long time!
Visual Studio 2017 Dev Cmd Prompt
"D:\CompanyName\ProductName.proj" (default target) (1) ->
target) (16) ->
(Build target) ->
C:\Program Files (x86)\MSBuild\InstallShield\2016\InstallShield.targets(77,3)
: error : -7159: The product license has expired or has not yet been initialize
Do I need to change something in a isproj or targets file or is this an InstallShield issue?
Thanks in advance,
I am guessing that your Development machine running IS Premier is licensed but your SAB (Stand Alone Build) machine is not. Your Premier license includes 5 SAB licenses.
Goto Software Downloads & License Center
Edited on 4/13/2017 to correct.
I have 4 versions of InstallShield on my main machine and when I double-click on any ISM file or try to open a Visual Studio project that includes an Installshield ISM there is no logic like you might find when opening a .SLN or .PROJ file and it knows which Visual Studio to use - Flexera doesn't have that ability to selected a particular version of InstallShield based on the ISM file being opened.
Here's a snippet from a conversation with Flexera. They have it as an enhancement, but it is a tough nut to crack without some rework of InstallShield.
Hi Chad, As long as Visual Studio is on the system when InstallShield is being installed, Visual Studio should automatically pick up InstallShield and allow for integration. If this was not the case, you can simply run a repair on the InstallShield installation after Visual Studio has been installed and the integration should be made then. Sincerely, Justin Flexera Software Technical Support firstname.lastname@example.org