PIX Error on experiment startup

So this was caused by my screen width and height to be garbage data when running through pix. The reason being was that my width and height I was reading from XML with with a file reference as such:


TiXmlDocument doc("Assets/XML/WindowsTweakables.xml");
if(!doc.LoadFile()) return;

When running through PIX it wasn't getting the proper file directory and returning so my variables from this file weren't being initialized. To fix this I tried the following:
project properties -> c/c++ -> preprocessor -> Preprocesor Definitions: and added this MY_SOLUTIONDIR=$(SolutionDir)

That creates a define with the full c:/ extension. Now I'm stuck on figuring out how to turn the define into a string since it doesn't include the quotes at the beginning and end. If anyone knows a cool way to turn it into a string that would be helpful =D


*UPDATE*:
MY_SOLUTIONDIR expands to something like: C:\Users\***\Desktop\***\TestProject\Debug\\


#define ADD_QUOTES_HELPER(s) #s
#define ADD_QUOTES(s) ADD_QUOTES_HELPER(s)

std::string filename(ADD_QUOTES(MY_SOLUTIONDIR));
**

For some reason the above doesn't work to add the quotes... instead I get:

warning C4129: 'D' : unrecognized character escape sequence
warning C4129: 'T' : unrecognized character escape sequence

Any 1337 macro programmers know how to fix this?

FYI, you can set the folder that PIX runs your executable in if click on the "More Options" button, and then go to the "Target Program" tab.

For some reason the above doesn't work to add the quotes... instead I get:

warning C4129: 'D' : unrecognized character escape sequence
warning C4129: 'T' : unrecognized character escape sequence

Any 1337 macro programmers know how to fix this?

The reason you get these two warnings is because the MY_SOLUTIONDIR expands to a path with backslashes (\) instead of forward slashes (/). Backslashes will be treated as the beginning of an escape sequence and, depending on the character following it, may be interpreted as some other random character (\\, \t, \r, \n are common ones)

Solution:
#define MY_SOLUTIONDIR "C:\\Users\\***\\Desktop\\***\\TestProject\\Debug\\"

or...

#define MY_SOLUTIONDIR "C:/Users/**/Desktop/***/TestProject/Debug/"

or you can do what MJP said

Neither of these are great solutions to the problem though. Your application should be capable of finding its resources regardless of the location it is run from. You can set the current working directory (on windows) to the executable directory using GetModuleFileName() and SetCurrentDirectory() so that your relative paths function correctly.

If you're targetting the 360 (XNA) then obviously you don't have to worry about any of this, and you can use one of the previous suggestions.