« Transferring your custom trace log files in Windows Azure for remote inspection | Main | Microsoft Most Valuable Professional (MVP) for Windows Azure [Architecture] »

12/29/2010

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

web casino

great. definetely i'm going to read your other posts...thank you.

UGG Outlet

Dear Friend, What is your new year resolution? In the New Year, may we have a new attitude and new behaviors. Best Wishes to you! And Happy New Year!

Andy Crsos

There is a workaround to make this work with SDK 1.3 one more time! It can be found here: http://blog.bareweb.eu/2011/03/workaround-wcf-trace-logging-in-windows-azure-sdk-1-3/

Thanks
Andy Cross

Christian Weyer

Thanks!

Or this ;)
http://weblogs.thinktecture.com/cweyer/2011/01/fixing-windows-azure-sdk-13-full-iis-diagnostics-and-tracing-bug-with-a-startup-task-a-grain-of-salt.html

BTW: the blog post you refer to refers to another one which in turn is based on my blog post mentioned here - phew...

But I am sure there will be an Azure SDK update very soon fixing all of this.

The comments to this entry are closed.


IMPORTANT: This is archived - and quite likely outdated - content, only kept online for reference purposes

Please visit thinktecture.com for up-to-date technical content.