Search Results

Search found 4 results on 1 pages for 'andyv'.

Page 1/1 | 1 

• Asp.net 4.0 site fails because no handler mapped with Classic appPool

  - by AndyV

  When I create a Asp.net app and flip the appPool to "ASP.NET v4.0 Classic" it fails with the following error: HTTP Error 404.17 - Not Found The requested content appears to be script and will not be served by the static file handler. After some searching it seems to be the handler not mapping correctly for the Classic mode but I can't find out where or how to fix that. I have the full .Net 4.0 install with VS2010 and the app works fine if I flip the appPool to Integrated. Also, it's a Windows 7 machine (I'm having the same problem on a Vista box). Thanks in advance. Andy

  Read the article

• Entity Framework Performance Inconsistency Compared to Sql Management Studio

  - by AndyV

  I'm getting timeouts with a very basic EF statement. I'm simply doing a select from a single table with a Entity.Title.StartsWith("test") and a .Take(25). When I run this for a search that returns no results I get a timeout. If I profile and grab the sql statement it looks fine, and if I run that sql in Management Studio it runs in a fraction of a second! Why would the same query run sub-second in Management Studio and timeout when generated by EF and called from an Asp.Net app?

  Read the article

• IIS7 Itegrated Pipeline Mode: Context.User is intermittently null for Windows Auth

  - by AndyV

  Our code relies on checking the Context.User.Identity value in the Global.asax Application_AuthenticateRequest(...) method to retrieve some information about the logged in user. This works fine in classic mode but when I flip IIS to use the Integrated Pipeline "Context.User" comes back as null, but only intermittently. Any ideas why? I have < authentication mode="Windows" and only Windows Auth enabled in the Virtual Directory.

  Read the article

• How to not have .axd files authenticate in IIS7

  - by AndyV

  We recently moved from IIS6 to IIS7 and we're experiencing some issues. The nastiest seems to be that .axd files being handled differently in IIS7. They're run through the pipeline for the authentication and authorization modules as well as the global.asax events. This causes problems for a variety of reason (specific to our code) that won't go into. How can we just exclude .axd files from all this like they were in IIS6? Thanks. Note: We're still in 32bit Classic pipeline mode.

  Read the article

1