远程连接到使用asp.net路由的Web表单应用程序？
我一直在开发一个使用.net路由与Visual Studio 2008的asp.net/c# Web应用程序。该项目设置为使用http：// localhost：17315作为服务器路径。我正在试图找到一种方法让同事从他们的系统连接到我的本地项目。当我将项目设置为IIS（5.1）中的虚拟目录时，.net路由无法正常工作，我收到404错误（http：// localhost / home）。
无论如何，我们本地网络上的用户是否仍然使用我当前的配置远程连接到我的应用程序？我知道他们无法连接到Visual Studio开发服务器，但我认为如果在IIS中设置应用程序，他们应该能够连接。也许这需要IIS6 +？
感谢您的帮助！
- Ian
I''ve been developing a asp.net/c# web application that uses .net routing with Visual Studio 2008. The project is setup to use http://localhost:17315 as the server path. I''m trying to figure out a way for a co-worker to connect to my local project from their system. When I setup the project as a virtual directory in IIS (5.1) the .net routing doesn''t work correctly and I get a 404 error (http://localhost/home).
Is there anyway for a user on our local network to connect to my application remotely with my current configuration? I know they can''t connect to the Visual Studio Development Server, but I would think they should be able to connect if the application is setup in IIS. Maybe IIS6+ is needed for this?
Thank you for your help!
- Ian
Localhost自动映射到127.0.0.1，这是一个映射到您自己的机器的内部地址，无论分配为外部地址的IP地址。
是有任何真正的原因，你不能改变它
\\ianoblePC：17315
因此无论您的IP如何，它始终有效（在您的本地网络内）地址？
Localhost automatically is mapped to 127.0.0.1, which is an internal address mapped to your own machine, regardless of the IP address assigned as an external address.
Is there any real reason you can''t change it to
\\ianoblePC:17315
So that it always works (within your local network) regardless of your IP address?
更多信息：对于tlhintoq的工作建议，您的网络需要能够解析托管Web应用程序的计算机名称。
-Frinny
Just a little bit more information: for tlhintoq''s suggestion to work your network is going to need to be able to resolve the computer name that is hosting the web application.
-Frinny
过去我改变主机文件以解析我的本地系统 http：// localfb 而不是localhost，但对于这个项目，似乎并不喜欢e ither。
从我读过的内容来看，如果我使用Visual Studio开发服务器，我将无法进行任何远程连接。所以我希望有一种方法可以在IIS中设置项目，因此.net路由仍然有效，并且可供我网络中的远程用户使用。
In the past I change my host file to resolve my local system to http://localfb instead of localhost, but for this project it doesn''t seem to like either.
From what I''ve read, if I use the Visual Studio Development Server I can''t have any remote connections. So I was hoping there was a way to setup the project in IIS so .net routing still works and it would be available to remote users in my network.