翻译强力驱动I've seen a few posts related to this topic but none with any conclusive answers...
When debugging my VS.NET 2010 app, I'm trying to start an external program whose location is relative to the project path. I've seen some indications that macros (like $(ProjectDir)) were supported in earlier versions of VS.NET, but they don't seem to work in VS.NET 2010. Using relative path notation just gives me an error that the path is invalid.
Has anyone run into this? If so, how did you address?
Thanks.
I know this is a little late to the party, but here's how we do it. The key to this is to set the 'OutputPath' explicitly to the Build directory. This re-bases it to working directory and not the VS install directory.
Update output path for the project to be:
Update StartProgram for the project to be:
Here is a sample configuration PropertyGroup:
AnyCPU true full DEBUG;TRACE prompt $(MSBuildProjectDirectory)\bin\ Program $(OutputPath)NServiceBus.Host.exe NServiceBus.Integration Similar to what Yobi21 suggested, editing the project file and adding these lines to the main
Program $(MSBuildProjectDirectory)\Path\Relative\To\CSProj\Folder Any Required Arguments Watch out for the properties in the
.csproj.userfile overriding those in your regular project file.
This one stumped me until I deleted the entries.
Found the answer here.
In the event that the above link goes dead, the summarized answer is as follows:
If Visual Studio.NET was launched by clicking on the SLN file in Explorer, the base path will be the folder (including the "\") where the SLN resides. Once I modified my relative path to account this and then launched VS.NET 2010 by double-clicking the SLN file, my external program correctly launched when hitting F5.
If Visual Studio.NET was launched from the shortcut on the Start Menu and then the SLN was opened from within Visual Studio.NET, the base path will be [Visual Studio install path]\Microsoft Visual Studio ["9.0" or "10.0" depending on whether using VS.NET 2008 or 2010]\Common7\IDE\.
I guess it makes sense now, but it still kinda stinks that VS.NET will only find my external program correctly depending on how I launch VS.NET.
$(SolutionDir) will not work if you use it directly in VS2010 in the start external programm, but if you close your solution and open the YourProject.csproj.user with notepad, you can change the path and include the $(SolutionDir).
Reopen VS 2010 and it works like a charm.
here an example of my project "ApplicationService_NSB.csproj.user"
Program $(SolutionDir)\Super\ApplicationService_NSB\bin\Debug\NServiceBus.Host.exe You can change the .user in notepad while solution is closed to even include relative paths. It is ,however, horrific. Example:
$([System.IO.Path]::GetDirectoryName($([System.IO.Path]::GetDirectoryName($(SolutionDir))))\MyCustomBindir\MyCustomProgram.exe
This is without scroll
$([System.IO.Path]::GetDirectoryName($([System.IO.Path]::GetDirectoryName( $(SolutionDir))
))\MyCustomBindir\MyCustomProgram.exe
The windows predefined folders can be used too.
$(AppData)\MyCustomBindir\MyCustomProgram.exe
Remeber the xml conifg .user file is parsed when loading the solution not when pressing the Start debug button so any changes to the .user file must happen while the solution is closed.
The list of available macros for vs2010 are listed in this web MSDN
ProjectDir macro are listed as available for VS2010
$(ProjectDir) The directory of the project (defined as drive + path); includes the trailing backslash '\'.
But if you're having throubles with it, you can try using SolutionDir.
$(SolutionDir) The directory of the solution (defined as drive + path); includes the trailing backslash '\'.