@alper thanks! I was hoping there is a proper angular way of doing vs removing, adding style classes by hand.
@alper - I understand your point and do not see MSFT investing into EF support for nosql, even so on their website its says that EF supports CosmoDB nosql! - Go figure.
There are other efforts to map EF and Mongo DB, see this thread as an example.
@ismcagdas - another good case for using nosql database where building app which uses unstructured data a way to go, which is pretty much every app built for the web this days. personally, I think a lot of business is lost for zero framework due to lack of nosql database support.
@alper - thanks, I know its easy to do, it was just a feature suggestion for Zero. When you create export, you want to pair with import function.
I was thinking simple upload file for now.
@alper - thanks. yes, we are on the same page. for sure it can be build. i am happy to wait for next release if its on your roadmap.
besides entity and db mapping, one needs to make sure its used just in time when needed.
in addition, it would be nice to allow flexible template config, so API can be used to send emails via backend by tenants.
@faisalalam - does it mean its on the list for next release?
@yekalkan - on your comment, let say I have field 'Name' in context of Animals. It should be prefix with that context, as if I have Name in context of tenants, they would not make sense.
@alper - do you mean, that you suggest to store those user custom template on the server or in database? What about upgrades or multihost system?
@bobIngham - thanks for the link,I will check out.
I just think a framework like zero should have an easy to use/customize email, and static content system.
Have you seen this link: <a class="postlink" href="https://www.aspnetzero.com/Documents/Extending-Existing-Entities">https://www.aspnetzero.com/Documents/Ex ... g-Entities</a>
