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,
we are building new ASP.NET zero applicacion arround existing database.
When mapping Entity.CreatorUserID (long) to SQL.CreatorID (int) we got mapping error.
So, is it possible to change IAudited to use int against long ?
Thanks for advance.
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,
we want to split single swagger documentation to multiple documents based on f.e. on modules.
In swashbuckle we can use ApiExplorer setting decorator atribute or custom convention.
How we can do it if we use dynamic generation of webapi controllers (CreateControllersForAppServices in .NET core version) ? Is there any parameter ?
Thanks for advance.
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.
I read "How to upgrade existing applications when a new version is available?" in FAQ. There is some main basic steps explained. Nothing more.
Is there some more details about upgrading in your docs, blobs or forums? Best practices, etc. How organize our code that upgrade should be easier ?
When i purchased Zero, i got vesion 3.05. Yesterday you published version 3.1 with many ng2 changes, Now i need to compare file by file.
Even everything will compile well, how i will know everything is made well ? I can make some security isues, because i missed some simple changes.
In future new upgrades will come. There Will be many many changes. Every upgrade can become nightmare.
Please advice.
Thanks for advance.
Edvin