查询XML CLOB列以获取列中的子XML(Query XML CLOB column to get sub XML in the column)

 您没有提到您正在使用的Visual Studio版本。 从内存来看，答案并没有太大变化，但我会回答Visual Studio 2015，因为这就是我的方便。 
 
 探索适用于所有Visual Studio版本的宏值的一种方法是使用ECHO命令。 将您的构建后脚本更改为 
 
echo TargetPath: "$(TargetPath)"
 
 并且您应该能够在构建项目时在“输出”窗口中读取宏的值。 在大多数现代版本的Visual Studio中，不应该使用Echo技巧。 
 
 在Post-Build Event属性页面中，单击Command Line字段末尾的下拉列表，然后单击<Edit ...>。 在Visual Studio 2015中，随后出现的对话框将显示命令行和评估值，以便您可以查看扩展了宏的命令行。 
 
 还有Macros >>按钮。 单击该按钮，您将看到一个对话框，显示每个宏名称及其值。 列表顶部的文本框允许您将结果过滤到包含字符序列的结果。 
 
 $(TargetPath)在此描述为“构建的主输出文件的绝对路径名（定义为驱动器+路径+基本名称+文件扩展名）” 。 这实际上意味着General属性页面上的Output Directory ， Target Name和Target Extension属性的值。 
 
 这里描述了 LIB工具。 要获得有关LIB运行的更多信息，您可以添加/ VERBOSE选项。 您也可以删除/ NOLOGO选项，这样您至少可以确认您正在运行LIB（并运行正确版本的LIB）。 
 
 很难说什么“无所作为”真正意味着什么。 我猜最可能的失败是要创建lib文件 - 但不是你期望的; 或者$（ProjectDir）\ Source中没有obj文件。 
 
 探索后一种情况的一种方法是将您的构建后事件更改为 
 
dir "$(ProjectDir)\Source\*.obj"
 
 然后检查构建输出以查看是否列出了obj文件。 如果目录中没有.obj文件，则输出窗口将显示类似的内容 
 
1>   Directory of C:\TestPrograms\vc.net.2015\VCConsole
1>
1>  File Not Found
 
 并且错误列表窗口将显示dir命令退出，代码为1。 

You don't mention what version of Visual Studio you are working with. From memory the answer doesn't change very much but I'll answer for Visual Studio 2015 because that's what I've got handy.
 
One way to explore macro values that should work for all Visual Studio versions is to use the ECHO command. Change your post-build script to be
 
echo TargetPath: "$(TargetPath)"
 
and you should be able to read the value of the macro in the Output window when you build the project. In most modern versions of Visual Studio, the Echo trick shouldn't be necessary however. 
 
In the Post-Build Event property page click on the drop-down at the end of the Command Line field and then click on < Edit...>. In Visual Studio 2015 the ensuing dialog will show you the command line(s) and the evaluated value so that you can see the command line(s) with the macros expanded.
 
There's also the Macros>> button. Click on that button and you'll get a dialog that shows every macro name and its value. The text box at the top of the list lets you filter results to those that contain a character sequence.
 
$(TargetPath) is described here as "The absolute path name of the primary output file for the build (defined as drive + path + base name + file extension)". What that really means is the value of the Output Directory, Target Name, and Target Extension properties on the General property page.
 
The LIB tool is described here. To get more information on the LIB run you could add the /VERBOSE option. You might also remove the /NOLOGO option so you at least get confirmation that you are running LIB (and running the correct version of LIB).
 
It's difficult to tell what "does nothing" really means. I'd guess the most likely failures are either the lib file is being created - but not where you expect; or there are no obj files in $(ProjectDir)\Source.
 
One way to explore that latter case would be to change your post-build event to
 
dir "$(ProjectDir)\Source\*.obj"
 
and then examine the build output to see if there are obj files listed. If there are no .obj files in the directory the Output Window will show something similar to
 
1>   Directory of C:\TestPrograms\vc.net.2015\VCConsole
1>
1>  File Not Found
 
and the Error List window will show that the dir command exited with code 1.