以编程方式运行MSBuild

Question

我正在尝试以编程方式执行MSBuild，但无法执行以下命令：

string command = string.Format(@"C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe  ""{0}\{1}.csproj""", _args.ProjectPath, _args.ProjectName);

这个字符串将被渲染为：

C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe  "C:\...\TestResults\Foo 2011-08-31 16_29_40\Out\Foo\solutionName\projectName\projectName.csproj"

我随后使用了新的ProcessStartInfo(command)。问题似乎是Foo和2011之间的空格。我得到以下输出：

MSBUILD : error MSB1008: Only one project can be specified.
Switch: 16_29_40\Out\Foo\solutionName\projectName\projectName.csproj

如何将项目文件传递给MSBuild？

- foo

---

相关问题（但使用PowerShell而不是原始的C#）- https://dev59.com/9HRB5IYBdhLWcg3w6LR2#473629 - Milan Gardian

Answer 1

我强烈建议您通过Microsoft.Build 命名空间中的类/接口来官方获取该技术。Microsoft在很多地方都使用了这个，因此这应该是有用的... 特别是类Microsoft.Build.Execution.BuildManager和Singleton Microsoft.Build.Execution.BuildManager.DefaultBuildManager是您要运行构建任务所需要的...源代码示例:

• http://social.msdn.microsoft.com/Forums/en-US/msbuild/thread/ec95c513-f972-45ad-b108-5fcfd27f39bc/
• 记录 MSBuild 4.0 构建消息

- Yahia

---

似乎无法使用这种方法进行 Web 应用预编译，你能帮我解决以下问题吗？ https://stackoverflow.com/questions/45605318/precompile-web-application-with-microsoft-build - Bandara

Answer 2

这里有一个带有简单记录器的完整工作示例。

构建解决方案的步骤：

using Microsoft.Build.Evaluation;
using Microsoft.Build.Execution;

string projectFileName = "C:\\Users...\\MySolution.sln"; // <--- Change here can be another
                                                         //      Visual Studio type.
                                                         //      Example: .vcxproj

BasicLogger Logger = new BasicLogger();
var projectCollection = new ProjectCollection();
var buildParamters = new BuildParameters(projectCollection);
buildParamters.Loggers = new List<Microsoft.Build.Framework.ILogger>() { Logger };
var globalProperty = new Dictionary<String, String>();
globalProperty.Add("Configuration", "Debug"); //<--- change here
globalProperty.Add("Platform", "x64");//<--- change here
BuildManager.DefaultBuildManager.ResetCaches();
var buildRequest = new BuildRequestData(projectFileName, globalProperty, null, new String[] { "Build" }, null);
var buildResult = BuildManager.DefaultBuildManager.Build(buildParamters, buildRequest);
if (buildResult.OverallResult == BuildResultCode.Failure)
{
    // Catch result ...
}
MessageBox.Show(Logger.GetLogString());    // Display output ..

还有记录器类（它是从 MSDN 的logger强烈派生的）：

public class BasicLogger : Logger
{
    MemoryStream streamMem = new MemoryStream();


    /// <summary>
    /// Initialize is guaranteed to be called by MSBuild at the start of the build
    /// before any events are raised.
    /// </summary>
    public override void Initialize(IEventSource eventSource)
    {
        try
        {
            // Open the file
            this.streamWriter = new StreamWriter(streamMem);
            //this.streamWriter = new StreamWriter(logFile);
        }
        catch (Exception ex)
        {
            if
            (
                ex is UnauthorizedAccessException
                || ex is ArgumentNullException
                || ex is PathTooLongException
                || ex is DirectoryNotFoundException
                || ex is NotSupportedException
                || ex is ArgumentException
                || ex is SecurityException
                || ex is IOException
            )
            {
                throw new LoggerException("Failed to create log file: " + ex.Message);
            }
            else
            {
                // Unexpected failure
                throw;
            }
        }

        // For brevity, we'll only register for certain event types. Loggers can also
        // register to handle TargetStarted/Finished and other events.
        eventSource.ProjectStarted += new ProjectStartedEventHandler(eventSource_ProjectStarted);
        eventSource.TaskStarted += new TaskStartedEventHandler(eventSource_TaskStarted);
        eventSource.MessageRaised += new BuildMessageEventHandler(eventSource_MessageRaised);
        eventSource.WarningRaised += new BuildWarningEventHandler(eventSource_WarningRaised);
        eventSource.ErrorRaised += new BuildErrorEventHandler(eventSource_ErrorRaised);
        eventSource.ProjectFinished += new ProjectFinishedEventHandler(eventSource_ProjectFinished);
    }


    void eventSource_ErrorRaised(object sender, BuildErrorEventArgs e)
    {
        // BuildErrorEventArgs adds LineNumber, ColumnNumber, File, amongst other parameters
        string line = String.Format(": ERROR {0}({1},{2}): ", e.File, e.LineNumber, e.ColumnNumber);
        WriteLineWithSenderAndMessage(line, e);
    }


    void eventSource_WarningRaised(object sender, BuildWarningEventArgs e)
    {
        // BuildWarningEventArgs adds LineNumber, ColumnNumber, File, amongst other parameters
        string line = String.Format(": Warning {0}({1},{2}): ", e.File, e.LineNumber, e.ColumnNumber);
        WriteLineWithSenderAndMessage(line, e);
    }


    void eventSource_MessageRaised(object sender, BuildMessageEventArgs e)
    {
        // BuildMessageEventArgs adds Importance to BuildEventArgs
        // Let's take account of the verbosity setting we've been passed in deciding whether to log the message
        if ((e.Importance == MessageImportance.High && IsVerbosityAtLeast(LoggerVerbosity.Minimal))
            || (e.Importance == MessageImportance.Normal && IsVerbosityAtLeast(LoggerVerbosity.Normal))
            || (e.Importance == MessageImportance.Low && IsVerbosityAtLeast(LoggerVerbosity.Detailed))
        )
        {
            WriteLineWithSenderAndMessage(String.Empty, e);
        }
    }


    void eventSource_TaskStarted(object sender, TaskStartedEventArgs e)
    {
        // TaskStartedEventArgs adds ProjectFile, TaskFile, TaskName
        // To keep this log clean, this logger will ignore these events.
    }


    void eventSource_ProjectStarted(object sender, ProjectStartedEventArgs e)
    {
        // ProjectStartedEventArgs adds ProjectFile, TargetNames
        // Just the regular message string is good enough here, so just display that.
        WriteLine(String.Empty, e);
        indent++;
    }


    void eventSource_ProjectFinished(object sender, ProjectFinishedEventArgs e)
    {
        // The regular message string is good enough here too.
        indent--;
        WriteLine(String.Empty, e);
    }


    /// <summary>
    /// Write a line to the log, adding the SenderName and Message
    /// (these parameters are on all MSBuild event argument objects)
    /// </summary>
    private void WriteLineWithSenderAndMessage(string line, BuildEventArgs e)
    {
        if (0 == String.Compare(e.SenderName, "MSBuild", true /*ignore case*/))
        {
            // Well, if the sender name is MSBuild, let's leave it out for prettiness
            WriteLine(line, e);
        }
        else
        {
            WriteLine(e.SenderName + ": " + line, e);
        }
    }


    /// <summary>
    /// Just write a line to the log
    /// </summary>
    private void WriteLine(string line, BuildEventArgs e)
    {
        for (int i = indent; i > 0; i--)
        {
            streamWriter.Write("\t");
        }
        streamWriter.WriteLine(line + e.Message);
    }


    public string GetLogString()
    {
        var sr = new StreamReader(streamMem);
        var myStr = sr.ReadToEnd();
        return myStr;
    }


    /// <summary>
    /// Shutdown() is guaranteed to be called by MSBuild at the end of the build, after all
    /// events have been raised.
    /// </summary>
    ///
    ///
    public override void Shutdown()
    {
        streamWriter.Flush();
        streamMem.Position = 0;
    }

    private StreamWriter streamWriter;
    private int indent;

}

此外，请务必使用正确的MSBuild Framework组件（即不要使用“4.0”版本）（参见此处）。

- Malick

Answer 3

你需要使用ProcessStartInfo的Arguments属性来传递参数。

例如：

var p = new Process();
p.StartInfo = new ProcessStartInfo(@"C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe")      
p.StartInfo.Arguments = string.Format(@"{0}\{1}.csproj", _args.ProjectPath, _args.ProjectName)

p.Start();

然而，对于MSBuild，您应该使用官方方法，就像Yahia提到的那样。

- Wilka

---

您可能还想查看Path to MSBuild问题，而不是硬编码MsBuild.exe的位置。 - Alexei Levenkov