MSBUILDEMITSOLUTION不工作与.NET 4? [英] MSBUILDEMITSOLUTION not working with .NET 4?

查看:242
本文介绍了MSBUILDEMITSOLUTION不工作与.NET 4?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

在MSBuild的以前的版本中,你可以设置一个名为MSBUILDEMITSOLUTION的环境变量设置为1,以得到一个解决方案(.sln)文件可能被解析的XML版本。根据<一href="http://blogs.msdn.com/b/msbuild/archive/2010/07/09/debugging-msbuild-script-with-visual-studio-3.aspx">MSBuild团队博客,这仍然在随Visual Studio 2010中,但它似乎并不奏效的版本。

In prior versions of MSBuild, you could set an environment variable named MSBUILDEMITSOLUTION to 1 to get an XML version of a solution (.sln) file that could be parsed. According to the MSBuild Team Blog, that's still in the version that ships with Visual Studio 2010, but it does not seem to be working.

有没有人成功地得到这个工作用的MSBuild 4.0?如果是的话,需要什么?

Has anyone managed to get this working with MSBuild 4.0? If so, what is required?

(我们用它来查找和运行惯例为基础的单元测试与楠脚本。)

(We use this to find and run convention-based unit tests with an NAnt script.)

推荐答案

设置MSBuildEmitSolution = 1,然后构建命令行。然后,您应该看到附近MySolution.sln一个MySolution.sln.metaproj文件。

Set MSBuildEmitSolution=1 and then build from the command line. You should then see a MySolution.sln.metaproj file near MySolution.sln.

注:

  • 如果您打开命令提示符窗口,然后设置通过Sysetm设置了的环境变量,那么你必须打开一个新的命令提示符。
  • 您会觉得,你也可以使用的MSBuild /号码:MSBuildEmitSolution = 1 ,但你不能
  • If you open a command prompt window then set the env var via Sysetm Settings then you will have to open a new command prompt.
  • You'd think you could also use msbuild /p:MSBuildEmitSolution=1, but you can't.

这篇关于MSBUILDEMITSOLUTION不工作与.NET 4?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆