Project path or other macro in command-line parameters for console project in VS2010

user_349719 0
Viewed 5870

The debug tab of the project properties for a console application in VS2010 allows me to set command-line parameters to pass to the project whilst debugging.

I would like to set a parameter which is a path and the path is specific to each developer/machine, as it is a path which resides in the solution folder and each environment is different.

For pre- and post-build events, I can use macros such as $(ProjectDir), but I can't find a way to do this for command-line parameters - is there a way? A hack is fine, as long as it's not too awful!

Thanks

console-application projects-and-solutions visual-studio-2010
2 Answers

Macros can be used in command line arguments for C++ projects, see:

How to pass solution folder as parameter in command line arguments (for debug)?

You could have an empty C++ project "Set as StartUp Project" and change its "Configuration Properties -> Debugging -> Command" from "$(TargetPath)" (default for new projects) to "$(ProjectDir)..\OtherProjectRelativeDebugFolder\OtherProjectsOutputFileName.exe".

Since OtherProjectRelativeDebugFolder and OtherProjectsOutputFileName are relative and thus location independent you should be fine with that.

You said:

A hack is fine, as long as it's not too awful!

Is an empty project that produces an empty dll (unless you find a way to stop it, e.g. delete on post-build) too awful?

BTW. Environment variables aren't resolved in "Debug -> command line arguments" for C# either. I'll be experimenting on setting an environment variable, passing its name (because it isn't resolved) and reading it in the program. Passing the name is intended to show where the environment variable comes from, i.e. project settings.

Edit: I hoped to find a way to set the environment variable to the value of a macro, e.g. in a build event. A simple shell "set" command is not persistent, so it didn't work out. Instead I was able to use a relative path as working folder to get things work for me. I also found a workaround that uses a file for persistent storage: VS2010 - Project Macro Variables in Start Options Command Line Arguments

user_26964260
Related