Menu
After adding MVC MiniProfiler to my ASP.NET MVC 4 project, it complains about requiring System.Web.Mvc 3.0.0.0.
Is there any way to use MiniProfiler with ASP.NET MVC 4?
The following assembly redirect is already defined in web.config:
<dependentAssembly>
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="0.0.0.0-4.0.0.0" newVersion="4.0.0.0" />
</dependentAssembly>
314
The main difference between ASP.NET Core and ASP.NET MVC 5 is their cross-platform approach. ASP.NET Core can be used on Windows, Mac, or Linux, whereas ASP.NET MVC 5 can only be used for applications on Windows. The ASP.NET Core MVC is a framework for building web apps and APIs, optimized for use with ASP.NET Core.
ASP.NET MVC 4 is a framework for developing highly testable and maintainable Web applications that follow the Model-View-Controller (MVC) pattern.
Is the framework outdated? ASP.NET MVC is no longer in active development.
MiniProfiler is a library and UI for profiling your application. By letting you see where your time is spent, which queries are run, and any other custom timings you want to add, MiniProfiler helps you debug issues and optimize performance.
I just created a new asp.net mvc 4 project and used nuget to grab the latest miniprofiler package. It started up just fine. Have you tried this? If you are using nuget, perhaps you should try to remove the mini profiler and then test, then add it back.
On difference in my project however is that my assemblyIdentity line includes a culture:
<assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
