application-pool

问题 What are pros and cons of having dedicated application pools over keeping web applications in one default app pool? 回答1: Pros: Applications are isolated from each other, unless IIS goes with it, an app pool locking will only take out applications in that pool Ability to run applications under different ASP.NET runtimes, one pool for 1.1 another for 2.0 if needed Ability to have different app pool settings for more or less critical applications. For example a corporate website in ASP.NET might

问题 I have a strange problem, when I use application pool as a specific user in my website the Local Security Authority Subsystem Service (lsass.exe) goes high until the IIS hangs. It's happen in a few minutes for a load of 30 users and above. I'm using Windows server 2012R2 with IIS 8.5. APPPool Net 4 integrated mode. The pool identity is set to local Windows user. The website has his own application pool and no other website is install on this server. Also, the server is hyper-v virtual machine

问题 I have a strange problem, when I use application pool as a specific user in my website the Local Security Authority Subsystem Service (lsass.exe) goes high until the IIS hangs. It's happen in a few minutes for a load of 30 users and above. I'm using Windows server 2012R2 with IIS 8.5. APPPool Net 4 integrated mode. The pool identity is set to local Windows user. The website has his own application pool and no other website is install on this server. Also, the server is hyper-v virtual machine

问题 I'm involved in a project where, by adopting DevOps approach, a software (a Windows service acting as agent) has to be installed on the target servers to allow performing deployments remotely and autonomously. As background, we are talking here about a server managing the deployments remotely, different target servers (Windows 2008 R2) where the code is deployed. The servers are hosting IIS applications and the deployments consist in just replacing files and folders followed by app pool

问题 I want to get status of a Application Pool. I have vbscript taken from here. strArgAppPool = Wscript.Arguments.Unnamed.Item(0) Const noError = False ' Establish the connection to the WMI provider Set oWebAdmin = GetObject("winmgmts:root\WebAdministration") ' Search the AppPool passed as argument in the list of application pools Set oAppPool = oWebAdmin.Get("ApplicationPool.Name='" & strArgAppPool & "'") ' Create nice messages for pool states Select Case oAppPool.GetState Case 0

问题 I am just wondering why is restarting IIS 7 application pool consider a good practice? I know that it'll clean up orphan resources like threads or session state, but how does other web server deal with this kind of problem? Do java developer/admin have to restart weblogic/websphere/apache/tomcat every so often to clean up junk in memory? 回答1: Typically it's used to compensate for bad programming. Sometimes yours, sometimes third parties depending on the libraries you are using. And, as with

问题 Changes in ascx / aspx files - will it reset application? Sometimes on dev server they won't cause it whereas on live server I think it sometimes causes it. What is the rule? Thanks Pawel 回答1: It depends on how to deployed your application; ASP.NET Deployment If you deploy simply; copy the application files you have created from your development computer to the production; In this way your application will not be reset only the page .aspx , or the page having the user control .ascx will be

问题 i try create a new web-site using wix installation. it's ok there is no problem but i cannot assign a new or existing web app pool to new web-site. iis:website tag does not contains WebAppPool attribute. How can i assign web app pool to web-site. You can see my code bellow. thanks for helping. <Component Id="WEB_SITE_CONFIGURE_COMPONENT" Guid="{35087032-D049-48C8-BCAD-1FEFD0C06A25}" NeverOverwrite="yes" Shared="yes" Permanent="yes" Transitive="yes"> <Condition><![CDATA[WEBSITE_INSTALLTYPE<>2]

问题 We are using NServiceBus in a web application and each time we deploy our code to production, we have to delete the Temporary Files in the folder: C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files We are following the instructions here to fix this: http://www.nservicebus.com/faq/TypeNotRegisteredInSerializer.aspx I was wondering if there is a more permanent fix to this? I feel like I am fighting with this every time I deploy new code. What is the best way to handle this

问题 Sigle-Sign-On between a 4.0 framework application and a 2.0 framework application seems to be broken. I have an old application built on asp.net framework 2.0 and a new application built on asp.net framework 4.0 and I am attempting configure SSO between the two. I have done all the proper configruation of setting up the same machine key with identical validationKey, decryptionKey, validation, and decryption attributes as well as identical authentication name, domain, protection, and path