I have a .NET Core 2.0 solution which contains a class library project and an ASP.NET MVC project. The MVC project reference the class library. Class library has all the entity classes and DbContext using EF Core. Everything was fine up to that.
Then I added ASP.NET Identity to the MVC project. It creates a separate IdentityDbContext to create the identity-related entities. I want relationships (foreign keys) between the Identity user entity and some of my other entities (I am using code first migrations). And I don't want to do migrations twice from both DbContextes. What is the correct approach to use here?
Combine your two contexts into one. In other words, just make your original context inherit from IdentityDbContext, instead of DbContext and dump the one the Identity scaffold created for you.
Related
I have an ASP.NET Core 5.0 MVC application and a .NET 5.0 class library called Application.Data. Due to separation of concerns, I decided that the DbContext and migrations should be contained within the data library. The DDL migrations work perfectly, but I'm having issues seeding AspNetCore.Identity users from within the data library.
Simply put, I want to access a UserManager<MyUser> instance in order to invoke the CreateAsync/AddToRoleAsync methods, but the UserManager constructor takes eight parameters that then also need to be instantiated. My understanding is that I could inject the user manager using the AddIdentity method to the service collection of my MVC project, but since my DbContext is contained within Application.Data, I wouldn't be able to run migration commands from within the MVC project.
What is the best course of action here?
I have started to play around with ASP.NET Boilerplate framework. I want to keep my application-specific entities and services in two separate projects. This will keep the core framework project untouched.
However I am not sure if i have the entities in a separate project how will the migrations work. The module system in the documentation touches about the logic piece, but it does not talk about entities that are local to the module (so each module has its own entity that gets created when migrations take place).
What options do we have if we need to separate our entities and services to individual projects?
However I am not sure if i have the entities in a separate project how will the migrations work.
Migrations work based on the DbSet that you define for each entity in DbContext.
What options do we have if we need to separate our entities and services to individual projects?
So you can have the entities in a separate project.
Add a dependency on YourSeparateCoreModule to *EntityFrameworkModule:
[DependsOn(
typeof(AbpProjectNameCoreModule),
typeof(YourSeparateCoreModule), // Add this
typeof(AbpZeroCoreEntityFrameworkCoreModule))]
public class AbpProjectNameEntityFrameworkModule : AbpModule
Then add a DbSet for each of the entities.
I'm working on an ASP.NET Core 1.1 Project with EF Core in Visual Studio 2017.
I have an ApplicationUser.cs class and the corresponding ApplicationDbContext : IdentityDbContext<ApplicationUser>.
Additionally, I have a MyClass.cs class containing PersonA.cs and PersonB.cs both deriving from a class Person.
Next to that I have a second dbcontext file: MyClassBdContextbased on MyClass
My question is how can I use Identity for this second dbcontext.
In my website, a user can login consuming the ApplicatioUser class and should be additionally able to insert in the MyClassDbContext database an object of the class PersonA or PersonB taking over some of the login data. To be more precise: PersonA or PersonB could be the one who has loggedin.
My idea is to keep authentication and authorisation separated from my business-database.
Any help is appreciated
Regards
I have ASP 4.5 website with a dependency on the business logic project, which is a class library built using .Net v4.5. Recently to expand the development, I have planned to introduce additional website project which is ASP Core. For the same, I have added the dependency of the business logic project. The business logic currently evaluates the request, cookies and session related stuff through HttpContext.Current instance. Which isn't working when I am accessing the business logic through ASP Core website.
Access HttpContext.Current
I have gone through the above question, and can know that why HttpContext.Current appears as null when I access it through ASP Core. And the answer to it suggests to populate the reference type IHttpContextAccessor through dependency injection. Now, the problem is, this interface belongs to the library Microsoft.AspNet.Http, and I don't see a way to add this to my business logic project.
Someone please help me out to access HttpContext into my business logic project.
I had this exact same need. The way I solved it was to create my own interfaces that live in my class library and I use those to get access to the current HttpContext regardless of whether the library is running under a 4.5 http context or a MVC Core http context.
To explain further, both the ASP 4.5 framework and the ASP Core Framework have an HttpContext object with associated Request and Response objects but they are defined in different namespaces and neither framework knows about the other framework's namespace. So What I decided is that I needed my library code to have access to an IHttpContext that was defined in one of my namespaces. And that IHttpContext would use an IHttpRequest and IHttpResponse that were also defined in my library's namespace. And finally, that IHttpRequest uses ISession, IHeaders and ICookies that are defined in my namespace.
With these interfaces defined, in my ASP 4.5 website I can now at the web layer create an HttpContext class based on my IHttpContext and have that class basically wrap the ASP 4.5 HttpContext object. My HttpContext object could then be passed into my library for use.
And in my MVC Core website I can now at the web layer create an HttpContext class based on my IHttpContext and have that class basically wrap the MVC Core HttpContext object. My HttpContext object could then be passed into my library for use just like it was when I was running under the ASP 4.5 environment.
So in the end, my library doesn't know which HttpContext object (4.5 or Core) it is actually accessing under the hood because it just knows that the object is has access to confirms to the IHttpInterface defined in it's library.
One final note, to help navigate name conflicts, I actually named my interfaces this way:
IAppHttpContext
IAppHttpRequest
IAppHttpResponse
IAppHttpSession
IAppHttpRequestHeaders
IAppHttpRequestCookies
Note that not all the functionality that is available in HttpContext 4.5 is available in MVC Core. The two are very similar but there are a few differences. The biggest difference is that MVC Core Session can only store byte arrays or strings whereas 4.5 session can store objects. So my IAppSession only supports storing byte arrays and strings and I have to make sure all my library's session needs work with that (all the objects that I need to store in session need to be serializable).
As you can imagine, implementing this is a bit of work, but in the end you will have a library that can access HttpContext and not care if it's running under a 4.5 HttpContext or a MVC Core HttpContext. Kinda neat.
Good luck.
i too had this same problem. I solved it by adding following dependency in my project.json file to add the http packages to class library
"Microsoft.AspNetCore.Http.Abstractions": "1.1.0"
then i used it like below
public class sampleclass
{
private readonly IHttpContextAccessor context;
public ISession GetSession()
{
return context.HttpContext.Session;
}
}
Thank you. Happy Coding :-)
Reference : http://benjii.me/2016/07/using-sessions-and-httpcontext-in-aspnetcore-and-mvc-core/
I want to implement custom membership provider in my project and I'm using repository pattern in my application.
Here is my project structure: (3 projects)
MyProject (Asp.Net MVC)
MyProject.Model (Entity model classes. I'm using entity framework)
MyProject.Repository (My repository classes)
Where do I implement the custom membership class? Since it's inherit from System.Web.Security; I should create in MyProject?
What is the right way to create custom membership class with Repository pattern?
I would suggest you to create one more project MyProject.Infrastructure that will contain your custom membership classes and other core components related to your application infrastructure.
You have to register the custom membership class through web.config so it's difficult for you inject the dependencies like your database repository to the class and so there is no much gain in implementing a repository pattern in your custom membership provider class. Anyway you have to instantiate a concrete repository implementation inside the membership class.