R
rjmarshall17
Guest
Hi,
I'm having an odd problem. It's only happen with one particular solution and when I try this in another, smaller, solution it appears to work fine. However in my larger solution if I define a CString as:
CString sTestString;
Looking at it in the debugger I see that the value of sTestString right after being defined is the executable path of the .exe I'm running. If I try to empty it, either with .Empty() or '= L"";', even if there was some other value in the string prior to emptying it, after the empty the string contains the executable path.
Has anyone else seen anything like this?
Thanks,
Rob
Continue reading...
I'm having an odd problem. It's only happen with one particular solution and when I try this in another, smaller, solution it appears to work fine. However in my larger solution if I define a CString as:
CString sTestString;
Looking at it in the debugger I see that the value of sTestString right after being defined is the executable path of the .exe I'm running. If I try to empty it, either with .Empty() or '= L"";', even if there was some other value in the string prior to emptying it, after the empty the string contains the executable path.
Has anyone else seen anything like this?
Thanks,
Rob
Continue reading...