Connect remotely to WebDev.WebServer.exe

问题:

1. Developing an ASP.Net website.
2. Running IE8.
3. Need to test website under IE6.
4. MultipleIE6 install broken by IE8 install (can't type in textboxes, yes I deleted cache, yes I re-registered the dll's).
5. Created VPC running IE6.
6. Can't connect to host WebDev.WebServer.exe.

Is there any way to configure WebDev.WebServer.exe so that it will accept remote connections?

回答1:

The workaround for the way that webdev.webserver is crippled to refuse remote requests is to use a lightweight proxy server running on the same host as webdev.webserver. The remote browser then uses the proxy and its requests appear to webdev.webserver like requests originating from localhost. I've used Privoxy succesfully.

Sample config:

• Configure Privoxy to listen on an IP address that is routable from your VM (eg 192.168.1.1:8118). You can put an IP address on a looback on your host OS and use NAT with the client OS.
• Configure your browser(s) in the VM to use 192.168.1.1:8118 for its proxy for all connections including localhost.
• Start your app in webdev.webserver
• With your VM browser go to the same URL as you would with a browser on your host OS (eg http://localhost:3254)

From the perspective of webdev.webserver the requests will originate from Privoxy on 127.0.0.1 and it will happily serve them up.

UPDATE These days, I am using Fiddler2 for this. Fiddler has an option in Tools > Options > Connections to "Allow remote computers to connect." But also note that IISExpress can be configured to accept remote connections.

回答2:

AFAIK, WebDev is coded to specifically reject all external connections... so the short answer would be "no".

Best thing to do would be simply publish the website to your VPC running IIS and test it that way.

回答3:

I ran into this same issue, and after some research, found that the method detailed at this site worked for me: http://www.funkymule.com/post/2009/04/17/Making-ASPNET-Development-Server-Listen-for-Remote-Connections.aspx

It involves modifying and reassembling the Webdev server and DLL, but once it's all up and running, I've been able to use older versions of Internet Explorer running in VPC/XP Mode to connect to the WebDev server running on the host machine via the internal network IP (192.168.x.x).

回答4:

Hmm i am not shure this works, but try adding the WebDev.WebServer.exe to be unblocked from your Windows Firewall.

If this doesn't work you have to install IIS and set a virtual directory directly on your development folder.

回答5:

I use one of Microsoft's VPC images to test IE6 using the debug webserver, so I don't know what could be causing your issues. Sounds like it could be a networking issue with the virtual machine.

Also IEtester works well for quick checks of rendering and functionality. I have yet to see any major differences between the behavior in IEtester and the real IE6 under XP, but the possibility exists so I still check with the virtual machine before release to production.

http://www.my-debugbar.com/wiki/IETester/HomePage