My company has some classic asp sites and developing new sites in asp.net, and everytime we create a new site in IIS 6 all the sites go down for a couple of seconds. So I'm thinking of changing the default value of the ASP.NET version to 2.x since that is what we're developing and I'm wondinger if these settings somehow affect the classic asp sites that are running on same IIS.
我的公司有一些经典的asp站点，在asp.net中开发新的站点，每次我们在iis6中创建一个新站点，所有的站点都会宕机几秒钟。我想改变ASP的默认值。净版本2。因为这就是我们正在开发的内容，如果这些设置在某种程度上影响了在相同IIS上运行的经典asp站点，那么我就不确定了。
All of them are asp.net 1.1 versioned right now but we have to get around this all-sites-down everytime we add a new site to IIS.
现在所有这些都是asp.net 1.1版本，但是每次我们在IIS中添加新站点时，我们都必须绕过这个全站点。
Any warnings? Anything I need to know etc?
任何警告?有什么我需要知道的吗?
Thanks a bunch.
多谢。
2 个解决方案
#1
1
All sites reset when you change the version of a site. Therefore, it is a good idea to change the default to the one you add the most.
当您更改站点的版本时，所有站点都将重置。因此，最好将缺省值更改为添加最多的值。
The default setting will not affect any existing sites, .net, classic or otherwise.
默认设置不会影响任何现有站点、.net、classic或其他。
The only issues you may have is that you cannot run a 1.1 virtual app within a 2.0 site.
您可能遇到的唯一问题是不能在2.0站点中运行1.1虚拟应用程序。
Also, you cannot run different versions in the same app pool. Therefore you should change the default app pool at the same as changing the default version.
此外，不能在同一个应用程序池中运行不同的版本。因此，您应该在更改默认版本的同时更改默认应用程序池。
As an aside, I have read of some command line options and other setting that mean you can change the version of a site without causing all of iis to reset. However, I have not managed to do this personally.
顺便提一下，我读过一些命令行选项和其他设置，这意味着您可以更改站点的版本，而不会导致所有iis重置。然而，我个人并没有做到这一点。
#2
1
Running a classic site along site a .Net site in the same app pool should be fine and you shouldnt see any down time in the IIS when you upload a new version to the server.
在相同的应用程序池中运行一个典型的站点，在同一应用程序池中，应该是可以的，当你上传一个新版本到服务器时，你不应该在IIS中看到任何停机时间。
You will find the server pause for a few seconds if you change the config of any app pool or if you change over the .Net version that is running in a site, all sites running in that app pool will be reset as the app pool resets.
如果你改变了任何应用程序池的配置，或者你改变了在一个网站运行的。net版本，你会发现服务器暂停了几秒钟，所有运行在该应用程序池中的站点将被重置为应用程序池重置。
My recomendation would be to create 2 App pools one for your new .Net 2.0 sites and one for the old classic sites, this will also help out if you are undergoing development as although unlikely it is possable to write code to complete crash the app pool.
我的建议是为你的新。net 2.0站点创建2个应用程序池，为旧的经典站点创建一个应用程序池，如果你正在进行开发，这也会有所帮助，尽管它不太可能有能力编写代码来完成应用程序池崩溃。
The only thing to remembger is that each app pool as a small memory overhead about 3-5MB so if you nmake an app pool for each site and host a large number of site you can very quickly run out of RAM.
唯一要记住的是，每个应用程序池作为一个很小的内存开销，大约3-5MB，所以如果你为每个站点建立一个应用程序池并托管大量的站点，你很快就会耗尽内存。
#1
1
All sites reset when you change the version of a site. Therefore, it is a good idea to change the default to the one you add the most.
当您更改站点的版本时，所有站点都将重置。因此，最好将缺省值更改为添加最多的值。
The default setting will not affect any existing sites, .net, classic or otherwise.
默认设置不会影响任何现有站点、.net、classic或其他。
The only issues you may have is that you cannot run a 1.1 virtual app within a 2.0 site.
您可能遇到的唯一问题是不能在2.0站点中运行1.1虚拟应用程序。
Also, you cannot run different versions in the same app pool. Therefore you should change the default app pool at the same as changing the default version.
此外，不能在同一个应用程序池中运行不同的版本。因此，您应该在更改默认版本的同时更改默认应用程序池。
As an aside, I have read of some command line options and other setting that mean you can change the version of a site without causing all of iis to reset. However, I have not managed to do this personally.
顺便提一下，我读过一些命令行选项和其他设置，这意味着您可以更改站点的版本，而不会导致所有iis重置。然而，我个人并没有做到这一点。
#2
1
Running a classic site along site a .Net site in the same app pool should be fine and you shouldnt see any down time in the IIS when you upload a new version to the server.
在相同的应用程序池中运行一个典型的站点，在同一应用程序池中，应该是可以的，当你上传一个新版本到服务器时，你不应该在IIS中看到任何停机时间。
You will find the server pause for a few seconds if you change the config of any app pool or if you change over the .Net version that is running in a site, all sites running in that app pool will be reset as the app pool resets.
如果你改变了任何应用程序池的配置，或者你改变了在一个网站运行的。net版本，你会发现服务器暂停了几秒钟，所有运行在该应用程序池中的站点将被重置为应用程序池重置。
My recomendation would be to create 2 App pools one for your new .Net 2.0 sites and one for the old classic sites, this will also help out if you are undergoing development as although unlikely it is possable to write code to complete crash the app pool.
我的建议是为你的新。net 2.0站点创建2个应用程序池，为旧的经典站点创建一个应用程序池，如果你正在进行开发，这也会有所帮助，尽管它不太可能有能力编写代码来完成应用程序池崩溃。
The only thing to remembger is that each app pool as a small memory overhead about 3-5MB so if you nmake an app pool for each site and host a large number of site you can very quickly run out of RAM.
唯一要记住的是，每个应用程序池作为一个很小的内存开销，大约3-5MB，所以如果你为每个站点建立一个应用程序池并托管大量的站点，你很快就会耗尽内存。