在XP Pro上的IIS 5.1下一次开发多个.net站点 [英] Developing more than one .net site at a time under IIS 5.1 on XP Pro
问题描述
大家好
我非常清楚XP Pro中包含的IIS版本是否有限，因为你只能创建IIS中的1个网站进入。
作为一个ASP.net开发人员，这是一个痛苦的屁股，因为我无法想象
out how停止让这个事实惹恼我的亲戚网址。
当我创建一个虚拟目录时 - 大概是你应该做什么
当你' '只允许一个网站我的相对网址'是指
*网站*的根，而不是VirDir的根。因此，如果我想开发更多
而不是一个应用程序我需要在网站根目录中拥有我的所有图像
文件夹 - 这是bollocks
我想到的唯一其他选择是在站点根目录的images目录中为每个
项目创建一个目录 - 这也是
bollocks因为在部署时我要么必须重新排列
我整个站点中的所有图像链接，要么将images目录复制到
$ b实时网站的$ b root。无论哪种方式都是它的混乱。
现在，我猜测微软并不是那么愚蠢，只能销售一种产品，只有
让你开发一个一次申请，但我和我的同事
还没有找到办法解决这个问题。
如果有人能解释我需要做什么让相对网址正常工作
非常感谢。好吧那实际上是用词不当。 VirDirs正在做他们应该做的事情，但这并没有帮助我一次开发多个应用程序。
就个人而言，我认为一个更好的解决方案是将连接
限制为大约3或4个并发用户并允许用户创建
很多开发网站尽可能。这样微软可以确定
减少的版本不会被用来托管多个用户的实时网站。
我甚至更喜欢它他们只允许来自localhost或
的连接，也许是本地局域网地址范围。无论哪种方式，他们必须有很多种方式，微软可以为开发人员提供他们需要的东西，并确保开发环境不会用于托管实际的实时网站。
正如我所说，我确定有一个解决方案。任何关于它实际是什么的建议
将非常感激。
谢谢大家。对上述内容的任何想法都非常好。
收到。
最基本的问候
thechaosengine
你好，
好吧，限制似乎是你只允许_run_一个
网站一次。但是，您可以创建多个网站，但不能使用
提供的GUI。
您可以使用WMI / ADSI创建网站，或者您可以使用Metabase
资源管理器。像这样的工具也可以让你创建多个网站，并且可以在它们之间轻松切换：
http://www.mindxpand.be/iisadmin/
-
问候，
Kristofer Gafvert
http：//www.ilopia .com
" Simon" < sh856531@microsofts_free_email_service.com>在消息中写道
新闻：OY ************** @ TK2MSFTNGP14.phx.gbl ...大家好
我非常清楚XP Pro中包含的IIS版本是否有限，因为您只能在IIS中创建1个网站。
作为一个ASP.net开发人员，这是一个痛苦的屁股，因为我无法想象如何停止这个事实激起我的相对网址。
当我创建一个虚拟目录 - 大概你应该做什么
当你只允许一个站点我的相对URL'是指
的根* * Site *而不是VirDir的根目录。因此，如果我想开发更多
比一个应用程序我需要在网站根目录'
图像文件夹中的所有图像 - 这是bollocks
唯一我想到的另一个选择是在站点根目录的images目录中为每个
项目创建一个目录 - 这也是
bollocks因为在部署时我要么必须要
重新排列整个站点中的所有图像链接，或将images目录复制到Live Site的
根目录。无论哪种方式都是它的混乱。
现在，我猜测微软并不是那么愚蠢，以至于销售一种产品，只需要b $ b只允许你一次开发一个应用程序，但是我的同事和我还没有想出办法来做到这一点。
如果有人能够解释我需要做些什么才能使相对URL正确地工作
，这将是非常值得赞赏的。好吧那实际上是用词不当。 VirDirs
正在做他们应该做的事情，但这并没有帮助我一次开发多个应用程序。
我个人认为更好的解决方案会将连接限制降低到大约3或4个并发用户，并允许用户创建尽可能多的开发站点
。这样微软可以肯定
减少的版本不会被用来托管多个用户的实时网站。
如果他们只允许来自localhost或者本地主机的连接，我甚至更喜欢它。
也许是本地局域网地址范围。无论哪种方式，微软都可以为开发人员提供他们需要的许多方式，并确保开发环境不会用于托管实际的实时网站。
说，我确定有一个解决方案。关于它实际上是什么的任何建议将非常感谢。
谢谢大家。对上述内容的任何想法都会得到非常好的收到。
最诚挚的问候
thechaosengine
"西蒙" < sh856531@microsofts_free_email_service.com>在消息中写道
新闻：OY ************** @ TK2MSFTNGP14.phx.gbl ...大家好
我非常清楚XP Pro中包含的IIS版本是否有限，因为您只能在IIS中创建1个网站。
作为一个ASP.net开发人员，这是一个痛苦的屁股，因为我无法想象如何停止这个事实激起我的相对网址。
当我创建一个虚拟目录 - 大概你应该做什么
当你只允许一个站点我的相对URL'是指*站点*的根目录而不是VirDir的根目录。因此，如果我想开发多个应用程序，我需要将所有图像都放在网站根目录的图像文件夹中 - 这就是bollocks
尝试使用类似〜/ images / something.gif的网址。 〜使URL相对于您的应用程序而言相对于该网站而言是
。
如果您的应用程序位于 http：// localhost / app / ，然后
~ / images / something.gif将 http：//localhost/app/images/something.gif 。如果
该应用程序正在 http://app.company中生产。 com / ，然后
~ / images / something.gif将 http://app.company.com/images/something.gif 。
这种形式的URL适用于标记为runat的所有元素= QUOT;服务器"这意味着
，如果你想在< img>中使用它元素，你需要做它< img
runat =" server" ......> ;.
John Saunders
2004年11月27日星期六20:47:12 -0000，" ; Simon"
< sh856531@microsofts_free_email_service.com>写道：
我很确定XP Pro中包含的IIS版本是有限的，因为你只能在IIS中创建1个网站。
作为一个ASP.net开发人员，这是一个痛苦的屁股，因为我无法想象如何停止这个事实惹起我的亲戚网址。
显而易见的解决方案是开发服务器，不在
工作站操作系统上运行。它不一定是你的系统，任何你可以上传文件的.NET服务器都能正常工作。
但这可以解决你的问题： />
http://www.mindxpand.be/iisadmin/
杰夫
Hi all
As I''m sure is common knowledge the version of IIS included in XP Pro is
limited in that you can only create 1 website in the IIS snap in.
As an ASP.net developer this is a pain in the arse because I can''t figure
out how to stop having this fact cock up my relative urls.
When I create a virtual directory - presumably what you''re supposed to do
when you''re only allowed one site my relative URL''s refer to the root of the
*Site* and not the root of the VirDir. As such, if i want to develop more
than one application i need to have all my images in the site root''s images
folder - which is bollocks
The only other option I''ve figured out is to create a directory for each
project in the images directory at the root of the site - which is also
bollocks because when it comes to deployment I have either have to rearrange
all the image links in my entire site or copy the images directory to the
root of the Live Site. Either way its messy.
Now, I''m guessing Microsoft aren''t so stupid as to sell a product that only
lets you develop one application at a time, but as yet my colleagues and I
havent figured out a way to do this.
If anyone can explain what I need to do to have relative URLs work correctly
that would be much appreciated. Well thats actually a misnomer. VirDirs are
doing exactly what they''re supposed to do but that doesnt help me develop
more than one application at a time.
Personally I think a much better solution would be to bring the connection
limit down to about 3 or 4 concurrent users and allow the user to create as
many development sites as possible. That way microsoft can be sure that the
cut down version isnt being used to host live websites to multiple users.
I''d even prefer it if they only allowed connections from the localhost or
perhaps the local lan address range. Either way their must be many many ways
that microsoft can give developers what they need and ensure that
development environments aren''t used to host actual live websites.
As I say, I''m sure there is a solution. Any advice on what it actually is
would be very much appreciated.
Thanks everyone. Any thoughts on the above would be very greatfully
received.
Kindest Regards
thechaosengine
Hello,
Well, the limitation seems to be that you are only allowed to _run_ one
website at a time. You can however create several websites, but not with the
provided GUI.
You can use WMI/ADSI to create the websites, or you can use Metabase
Explorer. A tool such as this also lets you create multiple websites, and
easily switch between them:
http://www.mindxpand.be/iisadmin/
--
Regards,
Kristofer Gafvert
http://www.ilopia.com
"Simon" <sh856531@microsofts_free_email_service.com> wrote in message
news:OY**************@TK2MSFTNGP14.phx.gbl...Hi all
As I''m sure is common knowledge the version of IIS included in XP Pro is
limited in that you can only create 1 website in the IIS snap in.
As an ASP.net developer this is a pain in the arse because I can''t figure
out how to stop having this fact cock up my relative urls.
When I create a virtual directory - presumably what you''re supposed to do
when you''re only allowed one site my relative URL''s refer to the root of the *Site* and not the root of the VirDir. As such, if i want to develop more
than one application i need to have all my images in the site root''s images folder - which is bollocks
The only other option I''ve figured out is to create a directory for each
project in the images directory at the root of the site - which is also
bollocks because when it comes to deployment I have either have to rearrange all the image links in my entire site or copy the images directory to the
root of the Live Site. Either way its messy.
Now, I''m guessing Microsoft aren''t so stupid as to sell a product that only lets you develop one application at a time, but as yet my colleagues and I
havent figured out a way to do this.
If anyone can explain what I need to do to have relative URLs work correctly that would be much appreciated. Well thats actually a misnomer. VirDirs are doing exactly what they''re supposed to do but that doesnt help me develop
more than one application at a time.
Personally I think a much better solution would be to bring the connection
limit down to about 3 or 4 concurrent users and allow the user to create as many development sites as possible. That way microsoft can be sure that the cut down version isnt being used to host live websites to multiple users.
I''d even prefer it if they only allowed connections from the localhost or
perhaps the local lan address range. Either way their must be many many ways that microsoft can give developers what they need and ensure that
development environments aren''t used to host actual live websites.
As I say, I''m sure there is a solution. Any advice on what it actually is
would be very much appreciated.
Thanks everyone. Any thoughts on the above would be very greatfully
received.
Kindest Regards
thechaosengine
"Simon" <sh856531@microsofts_free_email_service.com> wrote in message
news:OY**************@TK2MSFTNGP14.phx.gbl...Hi all
As I''m sure is common knowledge the version of IIS included in XP Pro is
limited in that you can only create 1 website in the IIS snap in.
As an ASP.net developer this is a pain in the arse because I can''t figure
out how to stop having this fact cock up my relative urls.
When I create a virtual directory - presumably what you''re supposed to do
when you''re only allowed one site my relative URL''s refer to the root of
the *Site* and not the root of the VirDir. As such, if i want to develop
more than one application i need to have all my images in the site root''s
images folder - which is bollocks
Try using a URL like "~/images/something.gif". The "~" makes the URL
relative to your application, not relative to the site.
If your application is located at http://localhost/app/, then
~/images/something.gif will be http://localhost/app/images/something.gif. If
the application is in production at http://app.company.com/, then
~/images/something.gif will be http://app.company.com/images/something.gif.
This form of URL works for all elements marked as runat="server" this means
that if you want to use it in an <img> element, you''ll need to make it <img
runat="server" ...>.
John Saunders
On Sat, 27 Nov 2004 20:47:12 -0000, "Simon"
<sh856531@microsofts_free_email_service.com> wrote:
As I''m sure is common knowledge the version of IIS included in XP Pro is
limited in that you can only create 1 website in the IIS snap in.
As an ASP.net developer this is a pain in the arse because I can''t figure
out how to stop having this fact cock up my relative urls.
The obvious solution is a development server, not running on a
workstation OS. It need not be your system, any .NET server that you
can upload files to will work.
But this may solve your immediate issues:
http://www.mindxpand.be/iisadmin/
Jeff
这篇关于在XP Pro上的IIS 5.1下一次开发多个.net站点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
