Visual Studio and .NET Framework Home
RoleManager.WriteToLog does not always work - 'message' does not appear in Development Fabric
8/5/2009 4:36:55 PM
User(s) can reproduce this bug
A local Development Fabric does not always display messages when RoleManager.WriteToLog is used. This behavior is random: sometimes it works, most of the time nothing is displayed.
Windows Azure SDK
Operating System Language
Steps to Reproduce
Requirements: install Visual Studio and the July 2009 Azure SDK CTP - details in http://msdn.microsoft.com/en-us/azure/cc972640.aspx
All of the my sample code was running on a local development fabric using local development storage (no Windows Azure hosted service or Windows Azure Storage account)
1) Download the "Azure Services Training Kit - April Update" from http://tinyurl.com/n9nrxr and install it.
2) Open C:\AzureServicesKit\Labs\BuildingWindowsAzureServices\Ex04-UsingWorkerService\end\End.sln
3) In WorkRole.cs, right after the call to client.LogMessage(), add a line that calls RoleManager.WriteToLog()
client.LogMessage("Pinging from Worker role");
RoleManager.WriteToLog("Information", "Pinging from Worker role");
4) Run (F5) the project.
I've been using the labs from the "Azure Services Training Kit - April Update" for three days now. Only once did the message from a call to RoleManager.WriteToLog() actually appeared in the development fabric.
In Internet Explorer, under http://127.0.0.1:81/Shoutbox.aspx you will see a series of "pings" from the worker role - for example:
8/5/2009 4:23:04 PM Pinging from Worker Role
8/5/2009 4:23:14 PM Pinging from Worker Role
8/5/2009 4:23:24 PM Pinging from Worker Role
In addition to the "pings" appearing in the Shoutbox.aspx page, I was expecting the same pings to appear in the development fabric.
Unfortunately, under the RDCOmpute_WorkerRole > 0 instance all I see is:
Role Instance: deployment 25).RDCompute.RDCompute_WorkerRole.0
Role state Started
I did right click and made sure the "Logging Level" was set to "Information".
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 1/8/2010 at 7:05 PM
Please try again with the November 2009 release of the Windows Azure Tools. This issue should be resolved.
Thank you for taking the time to share feedback on the product.
on 8/10/2009 at 9:28 PM
Thanks for your feedback.
We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.
to post a workaround.
Please enter a workaround.
© 2014 Microsoft