Using MVC Miniprofiler for every action call

前端 未结 2 1093
别跟我提以往
别跟我提以往 2021-02-02 00:10

Iv been experimenting the great tool, Mvc MiniProfiler.

I don\'t want to litter all my view with lots of Step commands, so I am wanting to use the profiler

相关标签:
2条回答
  • 2021-02-02 00:50

    You could define a global action filter:

    public class ProfileActionsAttribute : ActionFilterAttribute
    {
        public override void OnActionExecuting(ActionExecutingContext filterContext)
        {
            var profiler = MiniProfiler.Current;
            var step = profiler.Step("Action: " + filterContext.ActionDescriptor.ActionName);
            filterContext.HttpContext.Items["step"] = step;
        }
    
        public override void OnActionExecuted(ActionExecutedContext filterContext)
        {
            var step = filterContext.HttpContext.Items["step"] as IDisposable;
            if (step != null)
            {
                step.Dispose();
            }
        }
    }
    

    and register in Global.asax:

    public static void RegisterGlobalFilters(GlobalFilterCollection filters)
    {
        filters.Add(new HandleErrorAttribute());
        filters.Add(new ProfileActionsAttribute());
    }
    

    and that's pretty much all.

    0 讨论(0)
  • 2021-02-02 00:50

    It is alright to think and use ActionFilter. But MVC is still an ASP .NET application. To start and stop MiniProfiler at beginning and ending of each request, you can try the application events in Global.asax.cs file.

    // --------------------------------------------------------------------------------------------------------------------
    // <copyright file="Global.asax.cs" company="Believe2014">
    //   http://believeblog.azurewebsites.net/post/miniprofiler--log4net
    // </copyright>
    // <summary>
    //   The mvc application.
    // </summary>
    // --------------------------------------------------------------------------------------------------------------------
    
    using System;
    using System.Web;
    using System.Web.Http;
    using System.Web.Mvc;
    using System.Web.Optimization;
    using System.Web.Routing;
    
    namespace Mvc4Application
    {
    // Note: For instructions on enabling IIS6 or IIS7 classic mode, 
        // visit http://go.microsoft.com/?LinkId=9394801
    
        /// <summary>
        ///     The mvc application.
        /// </summary>
        public class MvcApplication : HttpApplication
        {
            /// <summary>
            ///     The application_ start.
            /// </summary>
            protected void Application_Start()
            {
                AreaRegistration.RegisterAllAreas();
    
                WebApiConfig.Register(GlobalConfiguration.Configuration);
                FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);
                RouteConfig.RegisterRoutes(RouteTable.Routes);
                BundleConfig.RegisterBundles(BundleTable.Bundles);
                AuthConfig.RegisterAuth();
    
                Profiler.Initialize();
            }
    
            /// <summary>
            /// The event when the application acquires request state.
            /// </summary>
            /// <param name="sender">
            /// The sender.
            /// </param>
            /// <param name="e">
            /// The event argument..
            /// </param>
            protected void Application_AcquireRequestState(object sender, EventArgs e)
            {
                Profiler.Start(HttpContext.Current);
            }
    
            /// <summary>
            /// This function is called by ASP .NET at the end of every http request.
            /// </summary>
            /// <param name="sender">
            /// The sender.
            /// </param>
            /// <param name="e">
            /// The event argument.
            /// </param>
            protected void Application_EndRequest(object sender, EventArgs e)
            {
                Profiler.Stop();
            }
        }
    }
    
    0 讨论(0)
提交回复
热议问题