It's really the strangest thing...
Running NUnit from TD.NET from within VS:
StoryQ_Report directory: C:\SVN\MyProject\trunk\code\output\StoryQ_Report
Running NUnit from TeamCity:
(so it's not a TeamCity work dir problem)
StoryQ_Report directory: C:\BuildAgent\work\5be4573062d36976\trunk\build scripts\StoryQ_Report
I've previously heard about Path.Combine (which gets used by SimpleHtmlFileManager) problems, but investigating the matter (e.g. http://stackoverflow.com/questions/53102/why-does-path-combine-not-properly-concatenate-filenames-that-start-with-path-dir)
doesn't help the case either.
I also tried using System.IO.Path.GetDirectoryName(typeof(DummyStoryFixture).Assembly.Location), but that yielded the same results.
For now, I'm using the hacky solution to just point at the "build scripts" folder as the artifacts folder in TeamCity, but it's really bad for maintainability and readability. As I said before, I'm in doubt whether this is a StoryQ problem,
but the previous version outputs the html files, one for each story, just fine in the output dir on the build server, and so does log4net as of now.
Whether to supply possibilities for defining the output dir or not... I think that's a good idea. If you want to save yourself from overload(s), wait for C#4 and optional params.
Thanks a lot for trying to help out!