blocks|key|759854|text|如果您在家中使用XP+Home进行业余工作，则无法在本地安装IIS。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|759855|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you do hobby work at home using XP Home, you can't install IIS locally.

blocks|key|759871|text|安装IISAdmin，您可以在IIS5中设置单独的站点，而不是使用虚拟目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|759872|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Install IISAdmin, and you can setup separate sites in IIS 5, instead of using virtual directories.

blocks|key|3007960|text|对于不想让开发人员在自己的计算机上有任何管理员访问权限来配置IIS的大型公司来说，内置服务器工作得很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3007961|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The built-in server works well for larger corporations that don't want to give developers any administrator access on their own machines to configure IIS.

blocks|key|3007995|text|内置服务器不是可配置的，而且它在一个奇怪的端口上运行，所以如果你指望特定的行为，它可能会很麻烦。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3007996|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The built-in server isn't as configurable, and it runs on an odd port, so if you're counting on specific behavior it can be troublesome.

blocks|key|3852226|text|Visual+Studio的内置web服务器名为Cassini，以下是它的一些限制……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3852227|3852228|它的每个端口只能承载一个ASP.NET应用程序。|unordered-list-item|3852229|它不支持HTTPS.|3852230|它不支持HTTPS仅响应本地主机请求。|3852231|与IIS|3852232|相比，它的启动较慢|3852233|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|E|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

The built-in web server for Visual Studio is called Cassini and here are a few of its limitations...

<ul>
<li>It can host only one ASP.NET
application per port.</li>
<li>It does not support HTTPS.</li>
<li>It does not support authentication.</li>
<li>It responds only to localhost
requests.</li>
<li>It is slow startup compared to IIS</li>
</ul>

blocks|key|5263469|text|如果您的项目驻留在IIS目录中，您仍然可以编辑代码。它只是取决于它是否已经发布。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5263470|当你调试某些基于权限的场景时，你会遇到很多关于Cassini和IIS的问题，比如Kerberos和NTLM身份验证，以及服务器压缩等问题。|offset|length|5263471|entityMap|0|LINK|mutability|MUTABLE|url|https://duckduckgo.com/html/?q=Wikipedia%2520ntlm|1|https://en.wikipedia.org/wiki/NT_LAN_Manager^0|0|14|8|0|1D|4|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]|$D|U|E|V|1|W]]|A|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]|N|$5|I|J|K|A|$L|O]]]]

If your project resides in the IIS directory you can still edit code. It just depends if it has been published or not.

You will run into so many issues on the Cassini vs. IIS when you are debugging certain permission based scenarios, like <a href="https://duckduckgo.com/html/?q=Wikipedia%20ntlm" rel="nofollow noreferrer">Kerberos</a> and <a href="https://en.wikipedia.org/wiki/NT_LAN_Manager" rel="nofollow noreferrer">NTLM</a> authentication as well as issues like server compression, etc. All in all, the Cassini is still okay to develop with, but make sure you do extensive testing when publishing to IIS.

blocks|key|5263519|text|如果您“web引用”内置web服务器上的web服务的URL，则端口可能会更改。除非您已经设置了菜单项目→属性选项页面中提到的“特定端口”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5263520|这是我现在已经习惯的东西。我总是设置一个特定的端口。现在，当well服务器有时崩溃时(我也遇到过这种情况)，我只需简单地更改端口号，一切都很好。我估计重启也能解决这个问题。|5263521|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you 'web reference' the URL for web services that are on the built-in webserver, the port might change. Unless you have set a "Specific port" mentioned in menu Project &rarr; Properties options page.

This is something I've gotten used to now. I always set a specific port. Now when sometimes the webserver crashes (I've had that happen), I simply change the port number, and all is well. I reckon restarting will also fix this.

blocks|key|760115|text|内置的服务器意味着开发人员不必知道如何设置IIS来测试他们的站点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|760116|你可能会争辩说，这是一个缺点，Windows开发人员至少应该了解那么多IIS。或者你可能会争辩说，一个不是系统管理员的开发人员根本不应该摆弄web服务器。|760117|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The built-in server means the developer doesn't have to know how to set up IIS to test their site.

You could argue this is a disadvantage, and that a Windows developer should know at least that much IIS. Or you could argue that a developer who isn't a system administrator shouldn't be messing around with the web server at all.

blocks|key|3852752|text|内置but服务器的健壮性稍逊于IIS，但不需要设置，因此这只是一种权衡。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3852753|您可能并不总是希望在IIS服务器(甚至本地IIS服务器)上公开您的开发项目，因此内置服务器对此很有帮助。|3852754|但是，如果您的应用程序要访问web应用程序规范之外的资源，那么您可能希望在IIS中频繁调试，以便您的应用程序将以受限的权限运行，并且您可以看到痛点在哪里。|3852755|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The built-in webserver is a little less robust than IIS, but requires no setup so it is just a tradeoff. 

You may not always want your development projects exposed on your IIS server (even your local IIS server) so the built-in server is good for that.

However, if your application is going to access resources outside of the norm for a web app then you may want to debug frequently in IIS so that your app will run with restricted permissions and you can see where the pain points will be.

blocks|key|5263683|text|There's+a+bug+in+the+way+the+built-in+server+handles+HTTPModules+-有a+workaround，但我讨厌放入在生产中永远不需要的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5263684|entityMap|0|LINK|mutability|MUTABLE|url|http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=274696|1|http://www.lhotka.net/weblog/UpdateOnMyStrugglesWithTheASPNETDevelopmentServer.aspx^0|0|1S|0|1V|C|1|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]|$A|R|B|S|1|T]]|C|$]]|$1|D|3|-4|5|6|7|U|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]|L|$5|G|H|I|C|$J|M]]]]

<a href="http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=274696" rel="nofollow noreferrer" title="Using Custom Identities in ASP.NET fails when using the ASP.NET Developement Server">There's a bug in the way the built-in server handles HTTPModules</a> - there is <a href="http://www.lhotka.net/weblog/UpdateOnMyStrugglesWithTheASPNETDevelopmentServer.aspx" rel="nofollow noreferrer" title="Search the comments for &#39;John Lewicki&#39;">a workaround</a>, but I hate having to put in code that'll never be needed in production.

blocks|key|3008438|text|Visual+Studio+web服务器对路径中的//就不那么宽容了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3008439|它将拒绝提供像http://localhost:52632/main//images/logo.jpg这样的链接，而IIS可以这样做。|3008440|这是相当模糊的，但这意味着我们有很多修复工作要做，以消除所有的//发生。|3008441|entityMap^0|P|2|0|7|18|0|V|2|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@$9|S|A|T|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|U|8|@]|D|@]|E|$]]]|K|$]]

The Visual Studio web server is less forgiving about <code>//</code> in the path.

It will refuse to serve a link like
<code>http://localhost:52632/main//images/logo.jpg</code> where IIS will do.

That's pretty obscure, but it means we have a lot of fixing to do to get rid of all the <code>//</code> occurrences.

blocks|key|760195|text|卡西尼号也不支持ASP+Classic页面。这只是一个遗留项目的问题，旧的ASP+Classic页面仍然存在(比如我们的web应用程序在工作)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|760196|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Active_Server_Pages^0|8|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Cassini also does not support <a href="https://en.wikipedia.org/wiki/Active_Server_Pages" rel="nofollow noreferrer">ASP Classic</a> pages. This is only an issue for legacy projects where old ASP Classic pages still exist (like our web application at work).

blocks|key|757387|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|757388|您需要运行Visual+Studio才能使用它(在正常情况下，circumstances)|unordered-list-item|757389|It只响应本地主机，因此您不能将链接http://simon-laptop:37473/app1提供给朋友以通过网络查看您的站点|offset|length|style|CODE|757390|最大的缺点:更难使fiddler正常工作，因为本地主机流量不是通过代理发送的。|757391|757392|使用http://ipv4.fiddler:37473是让Fiddler使用它的最好方法。|757393|entityMap|0|LINK|mutability|MUTABLE|url|http://www.fiddlertool.com/^0|0|0|I|U|0|9|7|0|0|0|2|P|0^^$0|@$1|2|3|-4|4|5|6|W|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|X|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|Y|7|@$F|Z|G|10|H|I]]|8|@]|9|$]]|$1|J|3|K|4|C|6|11|7|@]|8|@$F|12|G|13|1|14]]|9|$]]|$1|L|3|-4|4|5|6|15|7|@]|8|@]|9|$]]|$1|M|3|N|4|5|6|16|7|@$F|17|G|18|H|I]]|8|@]|9|$]]|$1|O|3|-4|4|5|6|19|7|@]|8|@]|9|$]]]|P|$Q|$4|R|S|T|9|$U|V]]]]

<ul>
<li>You need to have Visual Studio running to use it (under normal circumstances)</li>
<li>It only responds to localhost, so you can't give the link <code>http://simon-laptop:37473/app1</code> to a friend to view your site over the network</li>
<li>Big disadvantage: it's harder to get <a href="http://www.fiddlertool.com" rel="nofollow noreferrer" title="Fiddler">fiddler</a> working, because localhost traffic isn't sent through the proxy.</li>
</ul>

Using <code>http://ipv4.fiddler:37473</code> is the best way to get Fiddler working with it.

blocks|key|760254|text|我经常两全其美，在IIS中创建一个应用程序，并使用内置的web服务器进行更有效的调试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|760255|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I often take the best of both worlds and create an application in IIS, and use the built-in web server for more efficient debugging.

blocks|key|3853032|text|Cassini旨在成为一个轻量级的测试test服务器。这个想法是开发人员不需要安装和配置IIS来测试他/她的应用程序。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3853033|如果您熟悉IIS，并且已设置好IIS，并且您的计算机可以处理它，请使用IIS。卡西尼号并不是一个替代品。|3853034|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Cassini is meant to be a lightweight test webserver. The idea is that a developer does not need to have IIS installed and configured to test his/her application.

Use IIS if you are familiar with it and you have it set up and your box can handle it. Cassini is not meant to be a replacement.

blocks|key|3008693|text|我们还看到了Visual+Studio内置服务器的一些问题，这些问题涉及到一些第三方控件，这些控件将脚本放在\aspnet_client文件夹中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3008694|由于当您不在IIS下运行时，该文件夹不在那里，因此控件不起作用。总是使用IIS并避免奇怪的问题似乎要简单得多。|3008695|entityMap^0|1I|E|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

We've also seen some issues with Visual Studio built-in server regarding some third-party controls which put their scripts in the <code>\aspnet_client</code> folder. 

Since the folder isn't there when you're not running under IIS, the controls didn't work. It seems a lot simpler to always work with IIS and avoid strange problems.

blocks|key|3853145|text|所有前面的回答都是很好的答案--这里有一个gottcha和Cassini，可能需要在destkop上使用IIS。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3853146|Cassini在开发人员的上下文中运行，而不是作为IIS用户(IUSR_、IWAM或WinXP+x64中的w3wp进程)运行。如果您的网站正在访问外部文件或创建临时文件，这可能会有点痛苦。当您的开发人员以桌面管理员身份运行时，这一点最为明显。|3853147|当您移动到服务器IIS时，您在Cassini中可以访问的某些内容的工作方式就不同了。带有IIS_WPG的CACLing通常只需要修复，但如果您的开发人员没有考虑到这一点，他们很快就会对他们的部署感到相当沮丧。|3853148|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

All the previous responses are great answers - here's one gottcha with Cassini that might require IIS on the destkop.

Cassini runs in the context of the developer, not as the IIS user (IUSR_, IWAM, or in WinXP x64, the w3wp process). This can be a bit painful if you've got a web site that is accessing external files or creating temp files. It is most evident when your developer is running as an Admin of their desktop.

When you move to the server IIS, something that you would have had access to in Cassini doesn't work the same. CACLing with the IIS_WPG usually is all it takes to fix, but if your developer is not thinking about this, they will quickly get quite frustrated with their deploy.

blocks|key|3008767|text|Cassini不支持虚拟目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3008768|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Cassini does not support virtual directories.

blocks|key|3853200|text|我发现的一个不同之处在于，开发服务器处理上传文件的方式与IIS不同。如果上传的文件大于您的Max_File_Size设置，则无法捕获错误。页面就会死掉并返回一个500。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3853201|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One difference I've found is that the development server handles uploading files differently than IIS does. You can't trap the error if the file being uploaded is bigger than your Max_File_Size setting. The page just dies and returns a 500.

blocks|key|5264231|text|我遇到的另一个缺点是在使用自定义IPrincipal/IIdentity的表单身份验证网站上。卡西尼号将在没有警告(或通知)的情况下切换AppDomains。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|5264232|检查这个blog+post上的more.The头痛，这让我放弃了卡西尼，转而使用IIS。|5264233|entityMap|0|LINK|mutability|MUTABLE|url|http://www.lhotka.net/weblog/UpdateOnMyStrugglesWithTheASPNETDevelopmentServer.aspx^0|G|A|R|9|1W|A|0|4|9|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|W|8|@]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|H|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

Another disadvantage I've run into is on a Forms authenticated website using custom <code>IPrincipal</code>/<code>IIdentity</code>. Cassini will switch the <code>AppDomains</code> without warning (or notice).

Check this <a href="http://www.lhotka.net/weblog/UpdateOnMyStrugglesWithTheASPNETDevelopmentServer.aspx" rel="nofollow noreferrer">blog post</a> for more.The headache on this made me drop Cassini and stick with IIS.

blocks|key|5264254|text|不能使用虚拟目录:(|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5264255|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You cant use virtual directories :(

blocks|key|3853300|text|在启用了UAC的Vista或Windows+7中使用IIS时，必须以管理权限运行Visual+Studio。如果这样做，就不能将拖放从shell拖到Visual+Studio中(即使您以管理员身份运行explorer.exe的实例)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3853301|出于这个原因，我在大多数项目中都使用Cassini。|3853302|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

When you use IIS in Vista or Windows 7 with UAC enabled, you must run Visual Studio with administrative rights. If you do this, you can't drag an drop from your shell to Visual Studio (even if you run an instance of explorer.exe as administrator).

For this reason I use Cassini for most projects.

blocks|key|3008906|text|另一个缺点是，它通过gloabal+asax文件发送每个请求，其中包括对图像和样式表的所有请求。这意味着如果你在里面有代码来处理文件名，比如查找，那么辅助文件也会被处理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3008907|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Another dis-advantage is that it sends every request through the gloabal asax file which includes all requests for images and stylesheets. This means if you have code in there which does things with the file names, such as a look up, then the auxillary files willget processed too.

blocks|key|3853354|text|仅供参考，64位Windows+XP随IIS+6一起提供。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3853355|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

FYI, Windows XP 64-bit comes with IIS 6.

blocks|key|3008952|text|看起来第三种选择很快就会出现：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3008953|IIS+Express。|offset|length|3008954|entityMap|0|LINK|mutability|MUTABLE|url|http://weblogs.asp.net/scottgu/archive/2010/06/28/introducing-iis-express.aspx^0|0|0|B|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

It looks like a third option is coming soon:

<a href="http://weblogs.asp.net/scottgu/archive/2010/06/28/introducing-iis-express.aspx" rel="nofollow noreferrer">IIS Express</a>.

blocks|key|757646|text|这是一个开始于2年前的旧线程。我只是在谷歌搜索的时候偶然发现了UtilDev+Cassini。在我看来很有前途。至少它有同时运行多个站点的能力。这个功能对我来说真的很有用，因为我在两个不同的网站上工作，并且必须使用IIS在它们之间不断切换。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|757647|entityMap|0|LINK|mutability|MUTABLE|url|http://ultidev.com/products/Cassini/index.htm^0|V|F|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

This is an old thread started 2 years ago. I just stumbled upon <a href="http://ultidev.com/products/Cassini/index.htm" rel="nofollow noreferrer">UtilDev Cassini</a> while googling. Looks promising to me. At least it has the ability to run multiple sites simultaneously. That feature is really useful for me, because I work on 2 different sites and have to continuously switch between them using IIS.

blocks|key|5264499|text|这里有第三种方法的理由:尽管UWS+Pro可能比Cassini更接近IIS+(尽管灵感来自Cassini，并且来自UltiDev+Cassini+fork的供应商)，但它的主要目的是与ASP.NET应用程序一起使用redistributable。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5264500|📷|atomic|5264501|​|5264502|entityMap|0|LINK|mutability|MUTABLE|url|http://ultidev.com/Forums/yaf_postst633_Welcome-to-UltiDev-Web-Server-Pro.aspx|1|http://ultidev.com/Forums/yaf_postst660_Creating-Installer-project-bundling-UltiDev-Web-Server-Pro-using-Visual-Studio.aspx|2|IMAGE|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/bf3854c82c46a4866dc49cc4f970fb8b.png|imageAlt^0|E|7|0|2Z|F|1|0|0|1|2|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]|$A|12|B|13|1|14]]|C|$]]|$1|D|3|E|5|F|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|G|3|H|5|6|7|19|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|J|$K|$5|L|M|N|C|$O|P]]|Q|$5|L|M|N|C|$O|R]]|S|$5|T|M|U|C|$V|W|X|-4]]]]

Here's a reason for a third way: although <a href="http://ultidev.com/Forums/yaf_postst633_Welcome-to-UltiDev-Web-Server-Pro.aspx" rel="nofollow noreferrer">UWS Pro</a> is probably closer to IIS than Cassini (although inspired by Cassini and is from the vendor of the UltiDev Cassini fork), its main purpose is to be <a href="http://ultidev.com/Forums/yaf_postst660_Creating-Installer-project-bundling-UltiDev-Web-Server-Pro-using-Visual-Studio.aspx" rel="nofollow noreferrer">redistributable</a> along with ASP.NET applications.
<img src="https://i.stack.imgur.com/sBI3W.png" alt="enter image description here">

blocks|key|3009124|text|此外，通过IIS，您不必担心自动记住并在本地主机url中设置愚蠢的端口号。这是一个时髦的东西，直接依赖于Cassini...big的痛苦。谁会想要记住一些无用的端口号。只要用IIS..plain简单地运行这个该死的网站就行了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3009125|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Also via IIS, you don't have to worry about automatically remembering and setting a stupid port number in your localhost url. That's something funky directly relied upon with Cassini...big pain in the ass. Who wants to remember some abritrary port number. Just run the damn site in IIS..plain and simple.

I've found that on some occasions I can edit the source while debugging. Are there any other advantages of using the Visual Studio built-in webserver instead of a virtual directory in IIS?

I'm using Windows&nbsp;XP on my development environment, and a local instance of IIS&nbsp;5. I work on several projects, so I use multiple virtual directories to manage all the different sites.

Are there any disadvantages?

What are the (dis)advantages of using Cassini instead of IIS?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我发现在某些情况下，我可以在调试时编辑源代码。在IIS中使用Visual Studio内置IIS服务器而不是虚拟目录是否还有其他优点？我在我的开发环境中使用Windows XP，并使用IIS 5的本地实例。我在多个项目中工作，因此我使用多个虚拟目录来管理所有不同的站点。有什么缺点吗？

问使用Cassini而不是IIS有什么(不)优点？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问使用Cassini而不是IIS有什么(不)优点？EN