As a side note ... I've recently moved over to https://logentries.com and
haven't looked back. I use the Nlog library to send the logs over to
LogEntries. It's more for test/prod machines (rather than local dev/one-box
enviros) but it might be useful to consider.... if you are going to move
away from Trace Listeners and go to something like Nlog.
Phil
On Wed, Jan 11, 2012 at 7:49 PM, David Burela <david.bur...@gmail.com>wrote:
> I'm trying to get some quick trace diagnostics going in my compute
> emulator.
>
> Prior to Azure SDK 1.3 you could just write
> System.Diagnostics.Trace.TraceInformation("Doing stuff");
> and it would output it directly to the compute emulator console. Was
> useful for seeing which instance is executing.
>
> After 1.3 they changed everything and it seems to change it with every new
> version of the SDK. This means that the information on the web is very
> conflicting.
> The most recent blogs I can find mention that the Trace.TraceInformation()
> call should still work, except you need to config a new trace listener in
> the web.config file.
>
> This listener is posted all over the web
> http://blog.bareweb.eu/2011/01/tracing-to-azure-compute-emulator-sdk-v1-3
> <system.diagnostics>
> <trace>
> <listeners>
> <add
> type="Microsoft.WindowsAzure.Diagnostics.DiagnosticMonitorTraceListener,
> Microsoft.WindowsAzure.Diagnostics, Version=1.0.0.0, Culture=neutral,
> PublicKeyToken=31bf3856ad364e35"
> name="AzureDiagnostics">
> <filter type="" />
> </add>
> </listeners>
> </trace>
> </system.diagnostics>
>
> But that causes a StackOverflowException to be thrown.
> In ideas?
>
> -David Burela
>
> _______________________________________________
> ozazure mailing list
> ozazure@lists.codify.com
> http://prdlxvm0001.codify.net/mailman/listinfo/ozazure
>
>
_______________________________________________
ozazure mailing list
ozazure@lists.codify.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozazure
