Ok. I understant.
Thanks. Edvin
Yes i noticed that.
I hope you will give me some magic solution. :D
Why did you decide to use bigint for users and related references. bigint takes 8 bytes . This is loss of DB space.
Each audited entity have 2 fields (creaded, modified).
I believe int (2, xxx,xxx,xxx+) should be enought for all users.
Edvin
Hi.
I tried this already. I still got exception:
Unhandled Exception: System.Data.Entity.Core.MappingException: Schema specified is not valid. Errors:
(17,12) : error 2019: Member Mapping specified is not valid.
The type 'Edm.Int64[Nullable=True,DefaultValue=]' of member 'CreatorUserId' in type 'Sebit.Core.EF.Drzava'
is not compatible with 'SqlServer.int[Nullable=True,DefaultValue=]' of member 'ReferentID' in type 'CodeFirstDatabaseSchema.Drzava'.
Somehow, it is also logical. We cannot save in64 into in32. Right ?
If we have generic IAudited like IAudited<int> this could be solved.
Thanks for any suggestion.
Edvin
Hi, i noticed that you have converted zero template to vs2017 and Will be shiped in next release - 3.3
What that means ? Will you still supporting VS2015 or you move developement to VS2017 ?
Can you give us date when version 3.3 Will be finished ?
Regards.
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:
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
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, 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,
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 your tip. But this was not problem.
In my module i already created 2 contexts:
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
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