iis-6

We are getting ready to do a an initial deployment of an ASP.net MVC app on IIS 6 running on Windows Server 2003. We've been reading about performance issues involving the use of extenionless urls in MVC applications specifically in the case of removing the '.aspx' extension from the controller portion of the url. Has anyone who has deployed an MVC app in the past experienced any performance degradation in this area? Was it noticeable, and was it worth it for having the cleaner URLs? Our application will rarely have to deal with more than 1000 or so concurrent users. Edit: Thanks for all the

I am implementing Gzip compression for CSS and JS files on my site and just need to double check something. Is the file compressed on every request? or is it collected and sent from the Temporary folder (if the file exists)? I just want to be sure that my files are not compressed on every request. Also, is this a default behaviour or do I need some extra configurtion? And last, do I need to worry or configure something when using hash tags in the path (to inform the browser that the file has changed) and static file compression? or it should work with no problem. Edit: I am just using static

My goal is to share images, css, js, etc. across multiple websites that are all hosted under the same parent virtual directory in IIS. Of course, I could hard code the images paths, but I'd hoped .NET had a method that could intelligently resolve URLs using the IIS configuration. Here is my file/virtual directory structure: Parent Site (Virtual Directory) default.aspx mypage.aspx otherpage.aspx images - logo.jpg css - site.css Subsite1 (Virtual Directory) - default.aspx - products.aspx Subsite2 (Virtual Directory) - default.aspx - products.aspx - miscellaneous.aspx Parent Site , Subsite1 , and

I am a developer trying to assist my server admin in figuring out how to get this issue corrected. But I have an app that is using WCF 4.0 configure-less setup to make RESTful webservices calls. Everything works fine locally but when pushed to my server all PUT and DELETE requests return a 403 forbidden error. After searching around I've been unable to find anything that seems to work, and I'm not sure if there is some logs that would help figure this out, I'm not a server guy and apparently neither is my "server guy". So any tips on where to point him or what might be causing this would be

Please somebody help me fix this issue. Umbraco application as parent on IIS6 has the following version of System.Web.WebPages.Razor. <sectionGroup name="system.web.webPages.razor" type="System.Web.WebPages.Razor.Configuration.RazorWebSectionGroup, System.Web.WebPages.Razor, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> <section name="host" type="System.Web.WebPages.Razor.Configuration.HostSection, System.Web.WebPages.Razor, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" /> <section name="pages" type="System.Web.WebPages.Razor

I am developing an ASP.NET site with C# on IIS 7, but I hope for an answer that will apply to IIS 6 as well. Part of this site is the ability to upload up to 5 images at a time. I have a nice algorithm to resize the image that is uploaded to my optimal size and ratio. So the only real size limitation I have is during the initial upload. I have modified my web.config to raise the packet limit from 4MB to 32MB. For the most part this takes care of my issues. My question comes in the rare cases that a user tries to load more than my limit. I can raise the limit, but there is always a chance a