PDA

View Full Version : Automation issues with Project Primary Outputs with MSBuild and IS 2013



tkwan1
10-08-2013, 11:46 AM
We are using MSBuild and TFS 2010 to automate builds using InstallShield 2013 Premier Edition with Virtualization(20.00.0000). We are having issues specifically with project outputs and we are getting error messages for all the projects primary outputs we'ved added under Files and Folders section.


(with verbose diagnostic on)

AdminExecuteSequence table successfully built (TaskId:2)
AdminUISequence table successfully built (TaskId:2)
AdvtExecuteSequence table successfully built (TaskId:2)
AdvtUISequence table successfully built (TaskId:2)
InstallExecuteSequence table successfully built (TaskId:2)
InstallUISequence table successfully built (TaskId:2)
Directory table successfully built (TaskId:2)
Feature table successfully built (TaskId:2)
FeatureComponents table successfully built (TaskId:2)
Component table successfully built (TaskId:2)
Loading File table (TaskId:2)


C:\Program Files (x86)\MSBuild\InstallShield\2013\InstallShield.targets (73): No outputs for project "Business" were provided, but the installation project references "Business.Built". [C:\Projects\SomeProjectName\Setup2\Setup2.isproj]

... (more outputs)

File table successfully built (TaskId:2)
Building MsiFileHash table (TaskId:2)
MsiFileHash table successfully built (TaskId:2)
Class table successfully built (TaskId:2)
Extension table successfully built (TaskId:2)
ODBCDataSource table successfully built (TaskId:2)






When we build this manually in VS2010 it works fine without issue.


I've opened up the ism file directly and found likes

<td>Business.Primary output</td><td>0</td><td/><td/><td/><td>1</td><td>&lt;Business1&gt;|Built</td><td>3</td><td/></row>


if I remove the &gt;|Built, MSBuild doesn't throw an error, but the installer doesn't work and gives primary output messages


So I am turning here for help now to get automation working for 2013



-----
Edit: some more details

This issue will happen with using MSBuild command line, but will not happen with devenv(Visual Studio 2010 compiler). I have to use MsBuild because that is what TFS supports and is recommended.

commands used
(VS Command)
devenv SomeProject.sln /rebuild Release /project Setup2 /projectconfig Release

(The setup project is part of the build with this configuration)
MSBuild SomeProject.sln /p:Configuration=Release /verbosity:diag

(ISproj build command)
MSBuild Setup2.isproj /p:Configuration=Release /verbosity:diag

smantry
10-09-2013, 06:25 AM
Hi,

Is there a way to get .WXS files virtualized ?

Thanks in advance.
Shekhar

DebbieL
10-09-2013, 09:49 AM
smantry,

Your question is not related to post #1 in this thread. Please create a new thread for your question, or post in an existing thread that is related to your question. The following forum pages have links to the version-specific InstallShield forums:
http://community.flexerasoftware.com/forumdisplay.php?133-InstallShield
http://community.flexerasoftware.com/forumdisplay.php?167-Legacy-Installer-Products

Thank you.

alexc
01-29-2014, 05:00 AM
Hi, Did you resolve this issue?

I am experiencing the same when using Limited Edition and Team City

Thanks

Alex


We are using MSBuild and TFS 2010 to automate builds using InstallShield 2013 Premier Edition with Virtualization(20.00.0000). We are having issues specifically with project outputs and we are getting error messages for all the projects primary outputs we'ved added under Files and Folders section.


(with verbose diagnostic on)

AdminExecuteSequence table successfully built (TaskId:2)
AdminUISequence table successfully built (TaskId:2)
AdvtExecuteSequence table successfully built (TaskId:2)
AdvtUISequence table successfully built (TaskId:2)
InstallExecuteSequence table successfully built (TaskId:2)
InstallUISequence table successfully built (TaskId:2)
Directory table successfully built (TaskId:2)
Feature table successfully built (TaskId:2)
FeatureComponents table successfully built (TaskId:2)
Component table successfully built (TaskId:2)
Loading File table (TaskId:2)


C:\Program Files (x86)\MSBuild\InstallShield\2013\InstallShield.targets (73): No outputs for project "Business" were provided, but the installation project references "Business.Built". [C:\Projects\SomeProjectName\Setup2\Setup2.isproj]

... (more outputs)

File table successfully built (TaskId:2)
Building MsiFileHash table (TaskId:2)
MsiFileHash table successfully built (TaskId:2)
Class table successfully built (TaskId:2)
Extension table successfully built (TaskId:2)
ODBCDataSource table successfully built (TaskId:2)






When we build this manually in VS2010 it works fine without issue.


I've opened up the ism file directly and found likes

<td>Business.Primary output</td><td>0</td><td/><td/><td/><td>1</td><td>&lt;Business1&gt;|Built</td><td>3</td><td/></row>


if I remove the &gt;|Built, MSBuild doesn't throw an error, but the installer doesn't work and gives primary output messages


So I am turning here for help now to get automation working for 2013



-----
Edit: some more details

This issue will happen with using MSBuild command line, but will not happen with devenv(Visual Studio 2010 compiler). I have to use MsBuild because that is what TFS supports and is recommended.

commands used
(VS Command)
devenv SomeProject.sln /rebuild Release /project Setup2 /projectconfig Release

(The setup project is part of the build with this configuration)
MSBuild SomeProject.sln /p:Configuration=Release /verbosity:diag

(ISproj build command)
MSBuild Setup2.isproj /p:Configuration=Release /verbosity:diag

meclipse
08-07-2015, 12:11 PM
I have the same problem, did you fix it?

Thanks
Luis

k.rogers999
07-08-2016, 11:19 AM
Is there a resolution to this?


We are using MSBuild and TFS 2010 to automate builds using InstallShield 2013 Premier Edition with Virtualization(20.00.0000). We are having issues specifically with project outputs and we are getting error messages for all the projects primary outputs we'ved added under Files and Folders section.


(with verbose diagnostic on)

AdminExecuteSequence table successfully built (TaskId:2)
AdminUISequence table successfully built (TaskId:2)
AdvtExecuteSequence table successfully built (TaskId:2)
AdvtUISequence table successfully built (TaskId:2)
InstallExecuteSequence table successfully built (TaskId:2)
InstallUISequence table successfully built (TaskId:2)
Directory table successfully built (TaskId:2)
Feature table successfully built (TaskId:2)
FeatureComponents table successfully built (TaskId:2)
Component table successfully built (TaskId:2)
Loading File table (TaskId:2)


C:\Program Files (x86)\MSBuild\InstallShield\2013\InstallShield.targets (73): No outputs for project "Business" were provided, but the installation project references "Business.Built". [C:\Projects\SomeProjectName\Setup2\Setup2.isproj]

... (more outputs)

File table successfully built (TaskId:2)
Building MsiFileHash table (TaskId:2)
MsiFileHash table successfully built (TaskId:2)
Class table successfully built (TaskId:2)
Extension table successfully built (TaskId:2)
ODBCDataSource table successfully built (TaskId:2)






When we build this manually in VS2010 it works fine without issue.


I've opened up the ism file directly and found likes

<td>Business.Primary output</td><td>0</td><td/><td/><td/><td>1</td><td>&lt;Business1&gt;|Built</td><td>3</td><td/></row>


if I remove the &gt;|Built, MSBuild doesn't throw an error, but the installer doesn't work and gives primary output messages


So I am turning here for help now to get automation working for 2013



-----
Edit: some more details

This issue will happen with using MSBuild command line, but will not happen with devenv(Visual Studio 2010 compiler). I have to use MsBuild because that is what TFS supports and is recommended.

commands used
(VS Command)
devenv SomeProject.sln /rebuild Release /project Setup2 /projectconfig Release

(The setup project is part of the build with this configuration)
MSBuild SomeProject.sln /p:Configuration=Release /verbosity:diag

(ISproj build command)
MSBuild Setup2.isproj /p:Configuration=Release /verbosity:diag