Hi Sebastien,
Please disregard this msg. It was mis-sent.
On Dec 28, 2012, at 8:17 AM, XY L <[email protected]> wrote:
> Done
>
> On Dec 20, 2012, at 5:25 AM, Sebastien Pouliot [via MonoTouch]
> <[email protected]> wrote:
>
>> On Thu, Dec 20, 2012 at 3:35 AM, Xy <[hidden email]> wrote:
>> > Yes, we are using:
>> > using NUnit.Framework;
>> >
>> > Yes, we are using the runner from MonoTouch. Yes, the output shows up in
>> > Application Output in MonoDevelop, but it does not show up when we run the
>> > same tests using the mtouch command line, and when we include
>> > --stdout=output it does not output to a file, either.
>> >
>> > Can you advise on how to fix this/other things to try?
>>
>> Since you use Touch.Unit then the link I gave you explains how you can
>> automate it, from build scripts, to get the output (locally or
>> remotely).
>>
>> Sebastien
>> _______________________________________________
>> MonoTouch mailing list
>> [hidden email]
>> http://lists.ximian.com/mailman/listinfo/monotouch
>>
>>
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://monotouch.2284126.n4.nabble.com/mtouch-stdout-not-writing-to-file-how-to-capture-output-tp4657872p4657881.html
>> To unsubscribe from mtouch --stdout not writing to file, how to capture
>> output?, click here.
>> NAML
>
--
View this message in context:
http://monotouch.2284126.n4.nabble.com/mtouch-stdout-not-writing-to-file-how-to-capture-output-tp4657872p4657905.html
Sent from the MonoTouch mailing list archive at Nabble.com.
_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch
