1

I'm having a problem with a trusted Silverlight 4 OOB app when it runs on a Mac.

In order to debug I'd really like to be able to capture the debug/trace information output by the app. (The problem is in in code running in a background thread so outputting debug information to the screen isn't practical and risks creating new issues.)

Ideally I'm looking for the Mac equivalent of DebugView, if there is one.
If not, any tips on other approaches to debugging htis will be greatly appreciated.

Matt Lacey
  • 65,560
  • 11
  • 91
  • 143
  • Ended up having the app write to a file rather than having any trace output. A bit disappointing. If you end up doing similar I recommend watching out for the size of the file with regard to the amount of allocated space in IsolatedStorage. If a trusted app write the file somewhere else. That will also make it easier to get at :) – Matt Lacey Apr 13 '11 at 23:52

1 Answers1

-1

In the past I have created a com visible dll in c# that simply uses the standard win32 outputdebugstring call to output debug info. This can then be called from within Silverlight using COM automation :-)

JPK82
  • 51
  • 5