Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6474689
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T06:37:02+00:00 2026-05-25T06:37:02+00:00

I have a asp.net project that uses mvc-mini-profiler. I was using version 1.7 of

  • 0

I have a asp.net project that uses mvc-mini-profiler. I was using version 1.7 of the NuGet package and I noticed that there is an updated package whose version is 1.9. I updated the package and now my code no longer compiles. The code that fails to compile is:

public static T GetProfiledContext<T>() where T : System.Data.Objects.ObjectContext
{
    var conn = GetStoreConnection<T>();
    if (_enableProfiling)
    {
        conn = ProfiledDbConnection.Get(conn);
    }
    return ObjectContextUtils.CreateObjectContext<T>(conn);
}

The compilation errors report the following issues:

  • ‘MvcMiniProfiler.Data.ProfiledDbConnection’ does not contain a definition for ‘Get’.
  • The name ‘ObjectContextUtils’ does not exist in the current context.

I noticed that I can create an instance of ProfiledDbConnection and pass it the connection and an object of type IDbProfiler, but I am not sure how I should obtain that object.

Regarding ObjectContextUtils, I have no clue of what I am supposed to use.

How can I fix these issues?


Update:

By following @monkeychatter’s recommendations, I managed to build the code. I now get the following runtime exception:

A null was returned after calling the ‘get_ProviderFactory’ method on a store provider instance of type ‘MvcMiniProfiler.Data.ProfiledDbConnection’. The store provider might not be functioning correctly.

By inspecting ProfiledDbConnection in ILSpy, I noticed that it no longer overrides the DbProviderFactory. That seems to be the cause of the error, since the base implementation returns null. Has anybody been able to work around this issue?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T06:37:03+00:00Added an answer on May 25, 2026 at 6:37 am

    I just went through the same and unfortunately most/all documentation shows the ‘old’ way. The majority of this functionality has been moved to the ProfiledDbConnection class itself. To get the ObjectContext extension on ProfiledDbConnection you also need to reference an assembly from the nuget package ‘MiniProfiler.EF‘. Below are the edits to get the equivalent code in 1.9.

    //reference extension from MvcMiniProfiler.Data
    using MvcMiniProfiler.Data;
    
    var conn = GetStoreConnection<T>();   
    if (_enableProfiling)   
    {   
        //conn = ProfiledDbConnection.Get(conn);   
        conn = new ProfiledDbConnection(conn, MiniProfiler.Current);
    }   
    //return ObjectContextUtils.CreateObjectContext<T>(conn);
    return conn.CreateObjectContext<T>();
    

    Update:
    Per your updated question I would replace the line in my previous solution as below. This includes an override to fix up the ProviderFactory issue:

        //conn = new ProfiledDbConnection(conn, MiniProfiler.Current);
        conn = new EFProfiledDbConnection(conn, MiniProfiler.Current);
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an asp.net mvc project that uses some search methods in a seperate
I have an Asp.net MVC project that modestly uses jQuery scripts. My views also
Hi I have a Visual Studio solution and an ASP.NET MVC project that uses
I have recently started a personal project that uses ASP.NET MVC (RC1 at the
I have an ASP.NET MVC project that uses a SQL Server Compact database. I
I have an existing asp.net webforms project that uses Microsoft's Enterprise DAAB for the
In visual studio, I have an asp.net 3.5 project that is using MS Enterprise
I have an ASP.NET MVC project and I have a single action that accepts
I have an ASP.NET MVC project with a form. In the Action method that
I've been working on an ASP.net MVC project that uses checkbox HTML Helpers in

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.