I'm using version 1.6 of the Windows Azure SDK. As I understand it, the emulated load balancer listens on 127.0.0.1 and the instances of the web apps are created at 127.255.0.[0,1...].
I need to do cross browser testing as I develop, so I created a load of Virtual machines via Virtual PC and Oracle VirtualBox with different browser configs. Unfortunately, I don't seem to be able to access the emulated load balancer nor the separate instances from any of the virtual machines as everything is bound to loopback addresses.
Does anyone have any ideas how I can do this? thanks!
Hm, I have not tested exactly your scenario, but it should work as I used similar approach for other types of tests. So here is the possible solution:
Configuration steps:
Note: It is very important that you shut down the portmapper before you run your Azure Emulator deployment, and start it after the deployment is complete. This is because when running PortMapper will try to get port 81 on all network interfaces (including the loopback). That would force the Azure Emulator to jump to port 82 instead.
Try to add more mappings to your IIS application.. + you need to have a loopback adapter configured at your virtual machine.
On Windows 7 the current "hack," AFAIK, is to go to (assuming default directory structure here):
and edit both:
and modify /configuration/appSettings to include an item obviously replace "YOUR IP ADDRESS HERE" with your actual IP address such as 192.168.1.71. Here is an example:
The debugger will still open to the origin 127.0.0.1:8* location but just replace 127.0.0.1 with your local IP address. Also, you will likely have to restart Windows 7 to get these changes to take effect and you want to edit the config files as administrator as they are protected.
Actually the easiest solution is to use PJS PassPort.
http://sourceforge.net/projects/pjs-passport/
Very easy. Just need to remember to run it as administrator.