VS2013 - 如何在使用外部程序的 C# 项目的命令行参数中传递解决方案文件夹 $(SolutionDir)

Question

I am building a C# adding for Excel. In order to debug it, I need to launch Excel.exe with a command line argument containing the Debug or Release path to the addin.

For example:

• Start External Program: C:\\Program Files\\Microsoft Office\\Office15\\EXCEL.EXE
• Command line argument "C:\\Dev\\Project1\\Project1\\bin\\Debug\\Project1-AddIn64.xll"

However, I would like to replace "C:\\Dev\\Project1\\Project1\\bin\\Debug" with an equivalent of $(SolutionDir) for C++ projects in VS. Is there a way to do this ? If it is not doable, is there a way to get around this ?

EDIT: please support me and get this added in VS by voting up the following idea: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/6350738-support-for-macros-in-debugging-command-line-argum

Answer 1

Indeed, the macros cannot be used in the Start Options | Command line arguments

I see two solutions:

1. As the current folder is set to the $(TargetDir) when you Start an application you could refer to the solution folder like this: ..\\..\\..\\ if the External program accepts a relative path. (I am not quite sure why you would ever want to refer to the solution folder, referring to the output/target folder makes more sense to me)

2. In the Post Build event (unregister) and register the component the way the component should be registered when deploying it (a proper setup). This way you only have to refer to Excel in the Start Action. This also immediately adds the benefit of testing a scenario that is more similar to production.

Answer 2

It's not exactly a fix, but this may help some people. If you create your project from the project template "Visual C#/ .NET Core /Console App" instead of "Visual C#/ Windows /Console App", this feature is supported. When I put "$(SolutionDir)" in the Application Arguments field on the Debug tab of the Project Properties window, it is expanded at run time. Note that you will need Visual Studio 2015 Update 3 or later.

Answer 3

I guess you could make use of post-build event to read in your file. @HansPassant explained it in VS2010 - Project Macro Variables in Start Options Command Line Arguments .

A short quote:

A possible workaround is a post-build event that writes a file that you read in your program. Like echo $(ProjectName) > "$(TargetDir)cmdargs.txt

You could substitute cmdargs.txt to appropriate file you want.

Answer 4

You CAN use the macros in the Command fields. I used procmon.exe to see what VS was looking for and indeed i could use $(SolutionDir)\\..\\Debug\\thetoolname.exe as my solution was not in the root. Im using VS2019 so AFAIK it is supported from this version but it most likely is supported in lower versions. Just use procmon to check the path that VS is attempting to resolve.