mvc-mini-profiler

Has anyone been able to get the MVC mini profiler working on IIS 6? I've set up the profiler in my application and it works perfectly in Visual Studio, IIS Express and IIS 7.5 but when I put the exact same application onto IIS 6 it won't work. The problem seems to be around loading /mini-profiler-includes.js, I just get a 404 response. I've checked the route table and the correct routes have been registered by the profiler but apart from that I'm not sure what else to try. On IIS 7, ASP.NET by default runs in integrated mode so the ASP.NET runtime will handle all requests, however on IIS 6 ASP

When I create my context using the below function the profiler shows about a 300ms increase from the standard EF (version 4) context creation method. Is there another way to do this that has better performance? It defeats the purpose of performance profiling as is. public static Models.MyEntities GetContext() { var profiler = MiniProfiler.Current; var sqlConn = new SqlConnection(ConfigurationManager.ConnectionStrings["MyConnString"].ConnectionString); var profiledConnection = MvcMiniProfiler.Data.ProfiledDbConnection.Get(sqlConn, profiler); return ObjectContextUtils.CreateObjectContext<Models

Edit Got the answer here So I wanted to check out MiniProfiler to troubleshoot some performance issues. Before using it on production code I wanted to try it out with the a sample so went ahead with creating a MVC 5 application. This is plain vanilla app that gets created with the template. Added this code in the Index() method of HomeController: var profiler = MiniProfiler.Current; using (profiler.Step("Set page title")) { ViewBag.Title = "Home Page"; } using (profiler.Step("Doing complex stuff")) { using (profiler.Step("Step A")) { // something more interesting here Thread.Sleep(100); }

I have a long running SQL query inside a page that I've sped up by using an async task: using System.Threading.Tasks; ... var asyncTask = new Task<ResultClass>( () => { using (var stepAsync = MiniProfiler.Current.Step("Async!")) { // exec long running SQL } }); asyncTask.Start(); // do lots of other slow stuff ResultClass result; using (var stepWait = MiniProfiler.Current.Step("Wait for Async")) { result = asyncTask.Result; } (Note that this syntax will be a lot nicer once C# 5 comes out with async and await ) When using MVC mini profiler I get the timing for "Wait for Async", but I can't get

I have an issue where we are using EF 4.3 Code First against an existing database. I want to use the Mini-Profiler with EF and call MvcMiniProfiler.MiniProfilerEF.Initialize(); However, since we don't actually create any of the tables, the dbo.__MigrationHistory and dbo.EdmMetadata tables do not exist. The profiler ends up crashing because they don't exist. Is there any way to make the profiler ignore these EF Code First specific tables? Thanks! EDIT: These are the exceptions I get: (They come separately) Invalid object name 'dbo.__MigrationHistory'. at System.Data.SqlClient.SqlConnection

I'm trying to get MiniProfiler to profile my database access but I'm running into problems. All the help I see out there seems to be for "code first" entity framework connections. My model was designed before the code first update was available this year and I used the designer to create the edmx model. (I've been using this for almost a year and it seems to be working for me) The example on the MiniProfiler documentation site doesn't make sense to me. I've tried a few variations of it but I'm having problems. My Model is called CYEntities, normally to instantiate an ObjectContext I just do

I looked up How could I instantiate a Profiled DataAdapter to use with MVC MINI PROFILER? but this also did not answer my question. I have some code like this in SqlDatasource class - protected SqlCommand sqlCommand; public SqlDatasource(String query, String connectionString) : this(connectionString) { this.sqlCommand.CommandText = query; } public DataTable getResults() { DataTable table = new DataTable(); SqlDataAdapter adapter = new SqlDataAdapter(this.sqlCommand); SqlCommandBuilder commandBuilder = new SqlCommandBuilder(adapter); adapter.Fill(table); return table; } I want a way to hook