Another Cause for the Resource interpreted as but transferred with Error

In a previous article, I described what could cause this error.  While helping a customer the other day, we discovered another culprit, password protecting a directory.  The solution is to put the resources (i.e. .css, .js, image files, etc.) in a location which is publicly accessible (i.e. not under directory tree which has been password protected).  I also think this error may be particular to Chrome’s Developer  Tools.  The customer was using Internet Explorer, and this was the error that was thrown instead:

SEC7113: CSS was ignored due to mime type mismatch.

Tip for Ajax Control Toolkit MultiHandleSlider

I wrote this tip down for myself when I had problems getting the Ajax Control Toolkit MultiHandleSlider to work correctly in my application years ago. If you’re having difficulties as well, try setting the ID and BehaviorID properties to the same value.

.NET Security Exception Error

I’ve been meaning to write a post on this for ages but I’ve always forgotten to take a screenshot until now. If you ever get this error thrown from your .NET application:

Security Exception

Description: The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application’s trust level in the configuration file.

Exception Details: System.Security.SecurityException: Request failed


This always means that you need to set your trust level to “Full” in your web.config file in order to correct the problem.  I’ve included the correct XML markup that you need to add/modify in your web.config file below:

< ?xml version="1.0" encoding="UTF-8"?>
  <system .web>
    <trust level="Full"></trust>