MSBuild Question 3 9/12/2006 6:49:16 PM 6/19/2008 12:15:52 AM Discuss the Microsoft build engine aka MSBuild. Jul 13, 2009 - I've been working for some time at automating the InstallShield build process from within an MSBuild script. After a successful attempt using an Exec task along with ISCmdBld.exe, I decided that I really wanted the InstallShield logging included in the MSBuild logging process. I came across the Microsoft.

1. Install Msbuild 16
2. Install Msbuild Without Visual Studio

I am having trouble building my.NET 2.0 c# solution file using MSBuild. The solution builds fine in the VS2005 IDE, but when using MSBuild from the command line or Visual Build Professional, I get build errors when it trys to build the InstallShield 12 project. Originally, I saw this problem with two different active project solutions. To isolate the problem, I created a new solution file which contains a windows application and an InstallShield basic MSI project which uses the primary output from my application project. In creating my MSI project, I needed to place the MSI project folder within my application folder, i.e.

WindowsApplication1 SetupProject, so that I would not get an error regarding not being able to find the csproj file. When I build using MSBuild, I get the following messages when using the MSBuild command: C: WINDOWS Microsoft.NET Framework v2.0.50727 msbuild InstallShieldTestBed.sln /p:Configuration=Release;Platform='Any CPU' - Microsoft (R) Build Engine Version 2.0.50727.42 Microsoft.NET Framework, Version 2.0.50727.42 Copyright (C) Microsoft Corporation 2005. All rights reserved. Build started 8/4/2006 8:56:34 AM. Project 'C: Luminex Software InstallShieldTestBed InstallShieldTestBed.sln' (default targets): Target ValidateSolutionConfiguration: Building solution configuration 'Release Any CPU'. Target Build: Target WindowsApplication1: Project 'C: Luminex Software InstallShieldTestBed InstallShieldTestBed.sln' is building 'C: Luminex Software InstallShieldTestBed WindowsApplication1 WindowsApplication1.csproj' (default targets): Target CoreResGen: No resources are out of date with respect to their source files.

Skipping resource generation. Target CoreCompile: Skipping target 'CoreCompile' because all output files are up-to-date with respect to the input files. I could be misdiagnosing, but it looks like the problem you are encountering is between the Visual Studio solution and the Visual Studio C# project. As such there's not much InstallShield is likely to be doing that hurts or helps the situation.

Tere jesa yar kaha song. You will certainly enjoy its beautiful melody.

For troubleshooting, I would suggest trying to create a new C# project (which creates a solution), and seeing if that will build. If so, then add an InstallShield project and check again. If so, try comparing the solution files.

If it fails at the first step perhaps something is broken with the build configurations. I tried the solution with only a c# project and it built fine.

Install Msbuild 16

I added the MSI project and without associating the output from the c# project to the MSI, it too built fine from the command line. However, as soon as I added the primary output from the c# project and tried to build, I got the OutputPath error from MSBuild. Is there something else I can check to diagnose this problem? Not to cloud the issue, but I have been experimenting with MSBuild command line options and got further into the build process before hitting another issue. I used the /p:OutputPath= option to set the OutputPath to my c# project bin folder and MSBuild gives the following error: C: Program Files MSBuild Macrovision IS12 Macrovision.InstallShield.targets(63,3): error: OutputGroups item 'C: Luminex Software InstallShieldTestBed2 Solution2 WindowsApplication1 obj Release WindowsApplication1.exe' of 'WindowsApplication1.Primary output' d oes not appear to exist. I don't know if this is progress or not, but the question now exists as to why InstallShield appears to be looking in obj Release for the primary output instead of bin Release.

Last edited by Scott Lindberg; at 01:33 PM. Reason: Additional information added to reply.

Install Msbuild Without Visual Studio

Using MSBuild to Build a Release from the Command Line Using MSBuild to Build a Release from the Command Line InstallShield 2015 Express Edition Note: If you use MSBuild to build Visual Studio solutions with InstallShield projects, MSBuild requires.NET Framework 3.5 or later. MSBuild provides an easy way to build a release from the command line on a machine on which Visual Studio is not installed. The only components that you must have installed on the machine are the.NET Framework and InstallShield. Place a copy of your Visual Studio solution on the machine, and run MSBuild. To use MSBuild from the command line: 1.

Open the Command Prompt window. Change the directory to the one that contains MSBuild.exe: C: Windows Microsoft.NET Framework Version Folder 3. Type the command-line statement to build the release build of the Visual Studio integration project. For example: MSBuild.exe C: Folder Containing My Visual Studio Solution My Solution.sln /property:Configuration=Release See Also InstallShield 2015 Express Edition Help Library June 2015 Copyright Information Contact Us.