Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In my winforms application, AppDomain.CurrentDomain.BaseDirectory is set to ‘C:\Projects\TestProject\bin\Debug\’
In my unit tests it is ‘C:\Projects\TestProject\bin\Debug’ (no final slash). Why is this?
[Edit] @Will : I am asking why the test project’s directory doesn’t have a trailing slash?
You may be asking one of two possible questions: Why are they different, or why the test project’s directory doesn’t have a trailing slash.
Assuming its the first: That’s where the code is executing from. When you debug the program, its compiled and the binaries are placed under the project’s \bin\debug directory. When you’re testing, you’re running the test’s binaries, which are compiled and placed under the test project’s bin\debug directory.
Assuming its the last: Possibly some obscure reason, possibly a bug, or possibly to catch people who are concatenating paths rather than using Path.Combine (naughty naughty!).
Well, I don’t know why it’s different. Test applications may be run within a custom CLR host; I think this may be the case as test apps do some weird stuff with private accessors that normally aren’t allowed within the standard CLR host. I’m only grasping at straws here as I don’t have any actual knowledge about how this stuff is actually being coded.
Anyhow, the workaround stands (Path.Combine). Nobody should be concatenating paths, as path delimeters can change.