That's great news @ismcagdas : ) Thanks!
Hi @FlexSolution! ASPNETZERO team has merged my pr. Changes will be available with upcoming v6.8. Please, see pr for details.
@FlexSolution, sounds good to me!
I'm not sure ASPNETZERO guys will read our comments since this question has been closed already - could you create a new issue on GitHub?
You are right @FlexSolution - thanks for pointing it out! I will implement the necessary changes and create a pr. One thing though: I will use 'Forename' instead of 'Firstname' for the new key to better match existing key 'Surname'.
Hi @FlexSolution! Please, specify the project-type and version you are using.
I'm currently playing around with editions - to be honest: I was a bit confused about this screen as well, when I tried changing some values. Obviously, editing an edition that is in production and already has tenants assigned is not a good thing to do - so I can perfectly understand the way it is implemented.
Still, I think it would be better to just disable the input fields instead of not showing them at all. Maybe adding additional information about creating a new edition and moving tenants instead of editing an existing edition!?
What do you think?
@FlexSolution that would be even better : ) Thanks for your comment!
I'm not sure whether this feature request belongs to ASP.NET Boilerplate repository or ASPNETZERO repository, that's why i post it here first.
Feature Request: I would like to have the possibilty to create private editions in ASPNETZERO.
Reason: Right now I can create multiple editions and everybody can see them and also subscribe to one of them. If I need to change some features for a certain tenant I can do so by simply editing the features of the particular tenant in tenant-management. So far, so good. If a tenant requests some sort of feature upgrade and is also willing to pay a little more for it, I would have to create a new edition in order to adapt pricing. But this new edition will be available to everybody, which I propably don't want (maybe just because there would be too many editions available with only tiny differences). Having private editions - which are not visible to the public - could be a solution to this use case, I think.
Hello @ismcagdas!
I was able to solve the problem - which was just me not understanding how feature declaration works :D
Sorry, I wanted to post an update here but then I forgot about it ...
Anyway, thanks for your reply!
