iis-7.5

We've come across a rather annoying bug in IIS7.5 where it occasionally removes the contents of the tag in the web.config. It doesn't just remove the contents at runtime, it actually physically updates the file. On our local machines it happens when we rebuild everything (which includes replacing application.config from source control) and on our server machines it happens on app pool restart. Both cases are intermittent. It seems to be happening because we have some config at the root of the config and some in a location tag. The reason we do this is because we have some virtual applications

I'm trying to handle all application exceptions within global.asax for an MVC 3 project and whilst everything is working correctly within Cassini, as soon as I deploy to IIS 7.5, IIS starts taking control away from my application and handles many exceptions itself. This has the consequences of bypassing my custom logging and also returning ugly views. I have a similar approach to Darin's answer to this question . Here's what I'm using at the moment. protected void Application_Error(object sender, EventArgs e) { var app = (MvcApplication)sender; var context = app.Context; var exception = app

I'm investigating Microsoft's reverse-AJAX sample wherein they use a long timeout in the ScriptManager <asp:ScriptManager ID="ScriptManager1" runat="server" AsyncPostBackTimeout="2147483647"> And a ManualResetEvent to control the wait: private ManualResetEvent messageEvent = new ManualResetEvent(false); public Message DequeueMessage() { // Wait until a new message. messageEvent.WaitOne(); } public void EnqueueMessage(Message message) { lock (messageQueue) { messageQueue.Enqueue(message); // Set a new message event. messageEvent.Set(); } } I've noticed that Setting AsyncPostBackTimeout to a low

I'm trying to use log4net with a RollingFileAppender on IIS 7.5 / Server 2008 R2. However, the configuration from my old IIS 6 / Server 2003 box doesn't appear to work anymore, I simply don't see any log files being created, here's what I've got setup: In Web.config (inside <configSections> ) <section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/> In the same file (inside <configuration> ) <log4net> <appender name="ConsoleAppender" type="log4net.Appender.ConsoleAppender"> <layout type="log4net.Layout.PatternLayout"> <conversionPattern value="%date [%thread]

I have the following structure for my web application: In my root web config, not in the Areas/Admin/Web.Config I have the following: <location path="Areas/Admin"> <system.web> <authentication mode="Windows"></authentication> <authorization> <deny users="*"/> </authorization> </system.web> </location> I have my own authentication working on the main root of the web site no problems by using the [Authorize] tag. Now for the Areas/Admin I'd like to use Windows Authentication. In IIS (Server 2008 R2 Machine), I have the Admin folder configured as an application: And when I click on Areas/Admin in

I'm using plupload to upload files to an ASP.NET WebAPI service. It works fine in Chrome, and it works fine in IE8/IE9 on my development machine. When I connect to the website on the actual server, however, uploading a file causes plupload's error handler to fire with an error code of -400 and an error message of "Security Error." Looking at the response and request headers everything looks ok. The response even contains the correct return value! I'm guessing this has something to do with using https, but I'm not sure and it does work correctly in Chrome. (Firefox has a completely different

I recently switched my applications from using ASP.NET impersonation to actually specifying the identity in the application pool. The reason for this was to make future use of async easier so the threads run as my service account. Since making the change the site has been experiencing some issues. On the day I made the change I am now seeing these event logs show up much more often (used to be 2-3 times per day, now it's 8-10 times per day): Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that