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
- :
- ISBuild.exe can not resolve Primary/Content output specified in Files and Folders
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 24, 2013
05:17 PM
ISBuild.exe can not resolve Primary/Content output specified in Files and Folders
I have a Visual Studio solution that has a Web Site, Installer class, and a Basic MSI project.
The Basic MSI project references the Installer class DLL as it contains the custom actions I wish to be performed during the web site install.
My problem is that I MUST build the Basic MSI through the command line, so I use ISCmdBld.exe, however because I have the web site and Installer class added under Files and Folders using the "Primary output" options, the ISBuild.exe tool gives an error because it can not 'resolve' primary outputs.
Instead, it suggests building using Visual Studio or the Visual Studio command line.
If I use Visual Studios command line build tool "devenv.exe" instead as suggested, it gives me an error because devenv.exe can't build InstallShield projects!
This seems like a catch-22... does anyone know how to get this to work?
I appreciate any help. Thank you.
The Basic MSI project references the Installer class DLL as it contains the custom actions I wish to be performed during the web site install.
My problem is that I MUST build the Basic MSI through the command line, so I use ISCmdBld.exe, however because I have the web site and Installer class added under Files and Folders using the "Primary output" options, the ISBuild.exe tool gives an error because it can not 'resolve' primary outputs.
Instead, it suggests building using Visual Studio or the Visual Studio command line.
If I use Visual Studios command line build tool "devenv.exe" instead as suggested, it gives me an error because devenv.exe can't build InstallShield projects!
This seems like a catch-22... does anyone know how to get this to work?
I appreciate any help. Thank you.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jun 27, 2013
10:20 AM
I found the solution.
Devenv.exe is able to build the solution when I manually change from specifying primary output, to specifying the actual DLL file.
I'd rather stay using primary output definitions, but this works well enough.
Devenv.exe is able to build the solution when I manually change from specifying primary output, to specifying the actual DLL file.
I'd rather stay using primary output definitions, but this works well enough.