Active Web Solutions made a library to connect hassle-free to any TCP ports even sitting behind network infrastracture firewall using AppFabric Service Bus. It was based on Port Bridge which Clemens Vasters explained here - but lighter.

 I tested it by publishing a WCF service in my development machine and consuming that service from other machine sitting behind firewall and different network domain. 

I also tried Port Bridge and they both rocks!

Check SocketShifter at Codeplex. 

Check Port Bridge here.

In Azure DevFabric when you used: Environment.GetEnvironmentVariable("RoleRoot") you'll get 'AppRoot' as your Role root.It is suffixed to what should be the root in Azure Cloud. For example, in your devfabric your application will reside in 

"C:\Source\MyCloudApp\bin\Debug\MyCloudApp.csx\roles\MyCloudAppWorker\approot\<your binaries goes here>"

 but when you deployed your application in the Cloud it will reside in the root directory like: "E:\<your binaries goes here>" or something.

 I can't find and I don't know how to distinguished when my application is running in DevFabric or Cloud so I use application settings to easily correct/append the root path. 

 In my config I have:

      <!--when in DevFabric use - 'AppRoot'; use blank '' if in Azure-->
      <Setting name="ApplicationRoot" value="AppRoot" />

then from my code I have:

            string root = RoleEnvironment.GetConfigurationSettingValue("ApplicationRoot");

            AppRoot = Path.Combine(Environment.GetEnvironmentVariable("RoleRoot"), root);

Microsoft launched Table Browser.

The Windows Azure TableBrowser is a web based application that gives you the ability to browse your Windows Azure Storage tables and create, edit, delete, and copy entities.

Here is how to add https endpoint in the Windows Azure Development Fabric. 

http://blogs.msdn.com/jnak/archive/2009/05/12/https-endpoint-on-windows-azure.aspx

The code was so simple. There were two projects: a webrole and worker role project. The webrole project accepts input message from the user and write it to Queue. The worker role on the otherhand keeps on reading the Queue and logs the message to the Fabric.  It's frustrating that I can't see the log I am writing using RoleManager.WriteToLog(). I can't also get the messages I added in Queue. It's more frustrating to know that that very same code runs in my colleagues machine.

So, what did I do? I just close the Visual Studio, exit the Development Fabric UI, re-open the VSTS and re-run the project. The logging and Queue runs smoothly. 

But I am still puzzled how that happens. How can we zure with Azure?