首先为ASP.NET应用程序数据库实现OWIN数据库上下文

Question

The book I'm reading says that I should use OWIN to get an instance of my database context for using Identity... but I'm using database first so I want to have an instance of my database context for use throughout my application.

I've implemented the 'Start' class for OWIN in the following way:

using Owin;
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using uQuiz.Domain;
using uQuiz.Domain.Concrete;
using uQuiz.WebUI.Infrastructure;

namespace uQuiz
{
    public class OwinStart
    {
        /// <summary>
        /// Configures OWIN
        /// </summary>
        /// <param name="app"></param>
        public void Configuration(IAppBuilder app)
        {
            app.CreatePerOwinContext<QuizEntities>(GetQuizEntities);
            app.CreatePerOwinContext<ApplicationUserManager>(ApplicationUserManager.Create);
        }

        /// <summary>
        /// Returns an instance of the QuizEntities database context for OWIN
        /// </summary>
        /// <returns></returns>
        public static QuizEntities GetQuizEntities()
        {
            return new QuizEntities();
        }
    }
}

As you can see, I have a function there that just produces a single instance of my database context QuizEntities , which is database first so automatically generated.

I know that it is normal practice to have a 'Create' method within your database context, but I can't do this because it is automatically generated.

My Questions:

• Is there a down side of creating an instance 'per OWIN' in this way?
• Is this an acceptable way of implementing it?
• Is it acceptable to use the same database context for Identity and other requests within the application?

Answer 1

You are creating a database context per OWIN context, not per OWIN. It's not a single instance. For each incoming request, a database context is created. So OWIN calls GetQuizEntities for each request to create a new database context.

Is there a down side of creating an instance 'per OWIN' in this way?

No, you must do it the way you are doing now, otherwise your db context will get bloated. Create a new db context per request. Right.

Is this an acceptable way of implementing it?

Yes it is.

Is it acceptable to use the same database context for Identity and other requests within the application?

I'm not sure what you mean there.