Thanks.
I try add DBSet<OrganizationUnit> to my module context and add raw data, But this is not good idea because my context using different schema (not dbo).
Then i try to derive my module context from AbpZeroDbContext. This still don't work because i use different schema name (not dbo).
Finally i decide to create another DbContext class derived from AbpZeroCommonDbContext<Role, User> just for seeding raw data through it.
Is this correct or there is another more clean solution ?
Edvin
Hi, hikalkan.
Thanks for all yours answeres.
Edvin
Hi.
I understand that DI infrastructure (Castle Windsor) and ORM (EF6 -> EF7) need to be changed for supporting .NET Core. But i don't understand what do you mean by
Db Mappings will be same if we continue to use Identity. But if we switch to Identity Core too, then it may change slightly.
Do you mean changing Identity system (ASP.NET Identity 2.2.1 to ASP.NET Core Identity 1.1.0) ? If so, then DB schema and DBMappings could change. Is this your point ?
So if all i wrote is correct then i becoming afraid.
My goal is to create application based on ASP.NET ZERO running on .NET Core. I purchased ASP.NET ZERO and now i have very good starting point for my application: modules, localization, security, user management, etc. Everything on full .NET framework.
In 2Q2017 i hope, new boilerplate will be released. How will ASP.NET ZERO consume it ? Will it be possible ? Without adjust it to new identity it will not be possible. Agree ? How much time will this adjustment take ? I know it is hard to tell, but ....
Maybe you should write how you see migration steps to .NET Core. And what components should be changed, adjusted, etc. Some of them we talk about already. Could you do that ?
I will be very grateful to you if you could share some vision. It will help me to make plans for next six months.
Regards.
Edvin
Hikalkan, thanks for both answeres.
So, if i'm using ASP.NET Zero, EF6 is only option in present time.
Correct ?
Edvin