Base solution for your next web application

Activities of "edvin"

Hikalkan, thanks for both answeres.

So, if i'm using ASP.NET Zero, EF6 is only option in present time.

Correct ?

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

Hi, hikalkan.

Thanks for all yours answeres.

Edvin

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

Creating another DBContext derived from AbpZeroCommonDbContext<Role, User> is not good idea.

Now i get error

AbpException: Found more than one concrete type for given DbContext Type (Abp.Zero.EntityFramework.AbpZeroCommonDbContext

when starting project.

I'm stucked.

Hikalkan, please advice.

Edvin

Hi. Thanks for your tip. But this was not problem.

In my module i already created 2 contexts:

  • first: for my entities - derived from AbpDbContext
  • second: for existing entities (users, organization units) - derived from AbpZeroDbContext<TUser, TRole .....

Of course both are register to DI.

When starting project i got error:

_AbpException: Found more than one concrete type for given DbContext Type (Abp.Zero.EntityFramework.AbpZeroCommonDbContext`2[Sebit.CIS.Authorization.Roles.Role,Sebit.CIS.Authorization.Users.User]) define MultiTenancySideAttribute with Host. Found types: Sebit.CIS.EntityFramework.CISDbContext, Sebit.CIS.EntityFramework, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null, Sebit.BPM.EF.BPMZeroDbContext, Sebit.BPM.EF, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null.

Abp.EntityFramework.DbContextTypeMatcher.GetDefaultDbContextType(List<Type> dbContextTypes, Type sourceDbContextType, MultiTenancySides tenancySide) Abp.EntityFramework.Uow.EfUnitOfWork.GetOrCreateDbContext

When starting ZERO application it seems that ABP found 2 DBContexts that match for required Repository: One from

Problem is solved now ! I remove my second context and just use existsing context from

Thanks for help.

Edvin

Hi,

If you didn't already you should look at <a class="postlink" href="https://vmware.github.io/clarity/documentation/datagrid">https://vmware.github.io/clarity/documentation/datagrid</a>

It is open source , very clean, well documented and there is some other components too.

I think they have some potential because are made with UX in mind.

Edvin

Hi, thanks for link.

That's all i needed. ;)

i suggest you to add new topic "Upgrading steps" to documentation and for start put that link and dependent links to it.

Regards.

Edvin

Hi again.

What about VS 2017 ? It's almost shiped.

What plans do you have with ASP.NET ZERO template ? Will you have 2 templates ? One for 2015 in json format and one for 2017 in xproj format ?

Edvin

Hi.

I hope you will find good solution for supporting both VS2015 and VS2017. VS2017 has a lot uf usefull features that we are waiting for:

  • better js, es6, typescript, ng2 support,
  • new .NET Core tooling,
  • etc.. So we are planning to upgrade to VS17 as soon as possible.

When we upgrade to VS17 all suggestions witten in this post Will not be useful anymore.

Maybe you should create survey and ask customers and other boilerplate users what plans they have. If most people are going to upgrade to vs17 you just .....

There is another option: two separate projects.

Please let us know when decision Will be made.

Edvin

Showing 1 to 10 of 14 entries