Actually that what i wanted to do, however I don't know of quick way to do it.
I couldn't find a way to tell msbuild to redirect the console output of the nbehave task into a file. Now that you mention it it sounds reasnoable that there should be such a way using some coomand line argument to msbuild.
I'm using console.writeline to output data that will help get a better understanding of what goes inside my steps and help me during debugging.
specifically I log inside exceptions in order to understand what goes wrong (when things goes wrong) and I'm looking for a clean mechanism to include them into the build output so far i didn't find a good way to include them inside the nbehave
I think that part of the problem is that im developing a visual studio add-in. this means that the tests are done using the automation model which basically doesn't wok inside a debugger, and if thats not enough I'm encountering specific issues only
when run as part of the build server so a simple debug (which would probably solve the problem real easy) is not really an option.
I think that it would probably be useful to have some sort of mechanism to log stuff into nbehave output file.
does this make sense?