How do I get back the usual Corona debug info that the simulator usually provides.

CoronaCards (Corona in native apps) CoronaCards for WP8
#1

Is there any way to see the output from corona so that I can tell where in a file the problems are?

This is when running under the visual studio emulator.

#2

Is there any way to see the output from corona so that I can tell where in a file the problems are?

This is when running under the visual studio emulator.

No problem. Found the solution in one of the other threads. Apparently I needed to set the debugger to native.

#3

Glad you figured it out.

For everyone else’s quick reference, you can see your print() output via Visual Studio’s “Output” panel by doing the following:

  1. Right click on your application project in Visual Studio.

  2. Select “Properties” from the popup menu.

  3. Select the “Debug” tab on the left.

  4. Go to the drop-down box under “Debugger Type\UI Task” and select “Native Only”.

  5. Run your application in debug mode.

Just be aware that print output has large performance impact on WP8 while attached to the Visual Studio debugger.  I’ve found that it takes about 3-4 milliseconds per print() statement.  The native C/C++ printf() functions, Win32 OutputDebugString() functions, and .NET System.Diagnostics.Debug.WriteLine() methods are just as expensive.

#4

Is there any way to see the output from corona so that I can tell where in a file the problems are?

This is when running under the visual studio emulator.

No problem. Found the solution in one of the other threads. Apparently I needed to set the debugger to native.

#5

Glad you figured it out.

For everyone else’s quick reference, you can see your print() output via Visual Studio’s “Output” panel by doing the following:

  1. Right click on your application project in Visual Studio.

  2. Select “Properties” from the popup menu.

  3. Select the “Debug” tab on the left.

  4. Go to the drop-down box under “Debugger Type\UI Task” and select “Native Only”.

  5. Run your application in debug mode.

Just be aware that print output has large performance impact on WP8 while attached to the Visual Studio debugger.  I’ve found that it takes about 3-4 milliseconds per print() statement.  The native C/C++ printf() functions, Win32 OutputDebugString() functions, and .NET System.Diagnostics.Debug.WriteLine() methods are just as expensive.