Gathering outputs from an MSBuild exec task

msbuild

I have a batch script that I want to call from an MSBuild project, and the documentation says I can't use output from the batch (either console / environment variables) in the MSBuild project.

Is there a workaround?

Best Answer

You can redirect the output of the command to a file using "> output.txt" and read that into a variable.

<PropertyGroup>
   <OutputFile>$(DropLocation)\$(BuildNumber)\Output.txt</OutputFile>
</PropertyGroup>
<Exec Command="dir > &quot;$(OutputFile)&quot;" />
<ReadLinesFromFile File="$(OutputFile)">
   <Output TaskParameter="Lines" ItemName="OutputLines"/>
</ReadLinesFromFile>
<Message Text="@(OutputLines->'%(Identity)', '%0a%0d')" />

Related Solutions

MSBuild Task syntax for deleting files

If you're looking to delete an entire directory you require the RemoveDir task:

<RemoveDir Directories="Path/To/Obj" />

And if you're wanting to delete the PDB files from bin you'll want the Delete task:

<Delete Files="Path/To/Bin/MyApp.pdb" />

Note that you cannot use wildcards in the Delete task, so if you have multiple pdb files you're have to provide an ItemGroup as an argument.

.net – Resolving MSB3247 – Found conflicts between different versions of the same dependent assembly

Change the "MSBuild project build output verbosity" to "Detailed" or above. To do this, follow these steps:

Bring up the Options dialog (Tools -> Options...).
In the left-hand tree, select the Projects and Solutions node, and then select Build and Run.
- Note: if this node doesn't show up, make sure that the checkbox at the bottom of the dialog Show all settings is checked.
In the tools/options page that appears, set the MSBuild project build output verbosity level to the appropriate setting depending on your version:
- Diagnostics when on VS2012, VS2013 or VS2015 (the message in these versions says you should use "Detailed", but this is plain wrong, you should use "Diagnostics")
- Detailed when you're on VS2010
- Normal will suffice in VS2008 or older.
Build the project and look in the output window.

Check out the MSBuild messages. The ResolveAssemblyReferences task, which is the task from which MSB3247 originates, should help you debug this particular issue.

My specific case was an incorrect reference to SqlServerCe. See below. I had two projects referencing two different versions of SqlServerCe. I went to the project with the older version, removed the reference, then added the correct reference.

Target ResolveAssemblyReferences:
    Consider app.config remapping of assembly "System.Data.SqlServerCe, ..." 
        from Version "3.5.1.0" [H:\...\Debug\System.Data.SqlServerCe.dll] 
        to Version "9.0.242.0" [C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\System.Data.SqlServerCe.dll]
        to solve conflict and get rid of warning.
    C:\WINDOWS\Microsoft.NET\Framework\v3.5\Microsoft.Common.targets : 
        warning MSB3247: Found conflicts between different versions of the same dependent assembly.

You do not have to open each assembly to determine the versions of referenced assemblies.

You can check the Properties of each Reference.
Open the project properties and check the versions of the References section.
Open the projects with a Text Editor.
Use .Net Reflector.

Best Answer

Related Solutions

MSBuild Task syntax for deleting files

.net – Resolving MSB3247 – Found conflicts between different versions of the same dependent assembly

Related Topic