This website uses cookies. By clicking OK, 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.
gareththegeek
Pilgrim
Apr 10, 2014
05:28 AM
jcoone wrote: Looks like it should have built in SingleImage configuration, which would produce only a setup.exe or an MSI file. On a TFS build server, when an InstallShield project is built, normally these setup files are put into an INSTALL subdirectory in the drop location of the build (buried several directories deep under the INSTALL directory.) Also verify that Configuration and Platform are both set to the expected values for the TFS build and that building in that configuration/platform combination locally does produce the installer files. Check this through the Solution "Configuration Manager" There is no INSTALL subdirectory in the drop folder. TFS build definition is using the Release build configuration. Building locally For Release produces the single image setup.exe as expected. The install shield project is set to build SingleImage configuration under the solution Release configuration. :confused:
... View more
Apr 09, 2014
02:43 AM
I have a solution in Visual Studio 2012 which contains multiple projects - a web application, some class libraries, a couple of database projects and an Installshield LE 2013 project. If I build the solution for Release, locally, the ISLE project creates and outputs a setup.exe and associated msi etc. However, if I build the solution with Release configuration through TFS 2013 build automation, the build succeeds, produces outputs for all projects and drops them in the drop location with the exception of the ISLE project. No setup.exe and no .msi files are created on the build machine. The tail end of the build log is included below on Detailed mode: I modified my islproj file to include an AfterGet target as suggested by This Post to avoid the -2200 error described there, and you can see this target in the log in case you are wondering why it's there... How can I ask the build agent to actually compile my installer? ....omitted other projects build logging.... Task "MSBuild" Global Properties: Configuration=SingleImage Platform= BuildingSolutionFile=true CurrentSolutionConfigurationContents= Release|x86 Release|x86 Release|x86 Release|x86 Release|x86 SingleImage Release|x86 SolutionDir=C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\ SolutionExt=.sln SolutionFileName=PROJECTNAME.sln SolutionName=PROJECTNAME SolutionPath=C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.sln 9>Project "C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.Setup.Full\PROJECTNAME.Setup.Full.isproj.metaproj" (9) is building "C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.Setup.Full\PROJECTNAME.Setup.Full.isproj" (10) on node 1 (default targets). 10>Building with tools version "3.5". 10>Target "AfterGet" in project "C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.Setup.Full\PROJECTNAME.Setup.Full.isproj" (entry point): Using "Exec" task from assembly "Microsoft.Build.Tasks.v3.5, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a". Task "Exec" Command: attrib -r "C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.Setup.Full\PROJECTNAME.Setup.Full.isl" Done executing task "Exec". 10>Done building target "AfterGet" in project "PROJECTNAME.Setup.Full.isproj". 10>Done Building Project "C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.Setup.Full\PROJECTNAME.Setup.Full.isproj" (default targets). 9>Done executing task "MSBuild". 9>Done building target "Build" in project "PROJECTNAME.Setup.Full.isproj.metaproj". 9>Done Building Project "C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.Setup.Full\PROJECTNAME.Setup.Full.isproj.metaproj" (default targets). 1>Done executing task "MSBuild". 1>Done building target "Build" in project "PROJECTNAME.sln". 1>Done Building Project "C:\Builds\1\PROJECTNAME\PROJECTNAME Release Build\src\PROJECTNAME\Trunk\PROJECTNAME\PROJECTNAME.sln" (default targets). Build succeeded. 0 Warning(s) 0 Error(s) Time Elapsed 00:02:02.06
... View more
Latest posts by gareththegeek
| Subject | Views | Posted |
|---|---|---|
| 836 | Apr 10, 2014 05:28 AM | |
| 887 | Apr 09, 2014 02:43 AM |
Activity Feed
- Posted Re: Installshield LE TFS Build succeeds but does not produce output on InstallShield Forum. Apr 10, 2014 05:28 AM
- Posted Installshield LE TFS Build succeeds but does not produce output on InstallShield Forum. Apr 09, 2014 02:43 AM
- Tagged Installshield LE TFS Build succeeds but does not produce output on InstallShield Forum. Apr 09, 2014 02:43 AM
- Tagged Installshield LE TFS Build succeeds but does not produce output on InstallShield Forum. Apr 09, 2014 02:43 AM
- Tagged Installshield LE TFS Build succeeds but does not produce output on InstallShield Forum. Apr 09, 2014 02:43 AM
- Tagged Installshield LE TFS Build succeeds but does not produce output on InstallShield Forum. Apr 09, 2014 02:43 AM
- Tagged Installshield LE TFS Build succeeds but does not produce output on InstallShield Forum. Apr 09, 2014 02:43 AM
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
Mar 18, 2019
12:11 PM
|
