IIS / ASP.NET - Run all Managed Modules for All Requests (RAMMFAR)

By
When initially creating an ASP.NET web application, RunAllManagedModulesForAllRequest is enabled by default. If enabled, every request that passes through the ASP.NET pipeline, is treated as a managed modules (or handlers). When all modules are managed, including static content, there are possible performance implications. If you are utilizing a distributed cache provider, such as App Fabric, an implication includes that all managed resources, including static content are passed to the distributed cache (as managed resources), which adds a level of overhead, even if not required. The solution to optimizing your web application, is to disable runAllManagedModulesForAllRequests (RAMMFAR), and add defined locations for your static resources within your web configuration file. The static resources can include but are not limited to CSS, Images, and Scripts.

Firstly, you will want to add location segments for each file/folder location, within the configuration element.

...

   
   
      
         
            
         
      
   
   
   
   
      
         
            
         
      
   
   ...
Once completed, you will see the following section, under system.webServer.
You will need to change the value of runAllManagedModulesForAllRequests to false. Also, if you were to stop here, you would potentially get errors from utilizing Bundles within your project, failing upon a Script Render. You will need to ensure you properly add the BundleModule to remediate the errors. 
  
     
   
      
      
      
      
      
      
      ...
Note: In some scenarios, there may be other bundles, that reference static resources that aren't directly accessible in your project. In this scenario, the respective bundle/handler may need to be added to the system.webServer section, similar to the BundleModule. One example, is MiniProfiler, which has resources located at /mini-profiler-resources. 

    ...

Comments

Post a Comment

Popular posts from this blog

C# - ListView Item Spacing (Padding)

By
I'm perplexed at the reasoning that the ListView control, has no direct spacing/padding property. I am utilizing the ListView in the capacity of images, using the View state, View.LargeIcon. There is a method to modify the spacing/padding between the ListViewItem(s). Initially, you'll need to add: using System.Runtime.InteropServices; Next, you'll need to import the DLL, so that you can utilize SendMessage, to modify the ListView parameters. [DllImport("user32.dll")] public static extern int SendMessage(IntPtr hWnd, int msg, IntPtr wParam, IntPtr lParam); Once completed, create the following two functions/methods: public int MakeLong(short lowPart, short highPart) { return (int)(((ushort)lowPart) | (uint)(highPart << 16)); } public void ListViewItem_SetSpacing(ListView listview, short leftPadding, short topPadding) { const int LVM_FIRST = 0x1000; const int LVM_SETICONSPACING = LVM_FIRST + 53; SendMessage(listview.Ha
Keep reading

C# / SQL - Performing Distributed Transactions

By
Distributed Transactions span across multiple processes, which when encapsulated by the distributed transaction manager, will either commit a successful transaction or rollback changes. Distributed Transactions have been available within .NET, since .NET Framework 2.0. The Default Isolation level is set to Serializable , which in usage, creates unnecessary blocking and deadlocks. Therefore, it is suggested you override the default isolation level to ReadCommitted, which reflects the default within SQL Server. /// /// This class is responsible for performing Distributed Transactions. /// public class DistributedTransactionUtility { /// /// The Distributed Transaction method which creates a Transaction Scope object /// and commits if there is no error and rollbacks, incase of exception. /// /// /// The method which performs multiple DB Transactions. /// public void DoDistributedTransaction(Action method) { // Initializes Transac
Keep reading

IIS / ASP.NET - Disabling Compatibility Mode/View (Internet Explorer)

By
In ASP.NET, if you need to disable compatibility view of the end users using your application, you can override the respective browser (Internet Explorer) compatibility mode, by setting the compatibility mode to Edge. By using this setting, the users of the web application, will render using the latest rendering engine available. If in the scenario you don't want to use the latest, you can also define other standards, such as IE8, IE9, etc. This can be defined in the master page/view using the following meta tag within the <head> section: ... Note: The X-UA-Compatible meta tag will need to be the first meta tag, in the circumstance that setting the IE rendering engine to Edge, is not working as intended. and web.config, by adding a custom header using X-UA-Compatible to the response headers, ...
Keep reading