Hi, guys once again thanks for these great frameworks ABP and Apbzero to my knowledge are the best frameworks for building DDD with .net at the time.
However, when dealing with junior developers most of the times its hard to explain everything and the best approach that I find are to make them learn by doing, or my copy pasting the code and making it fit for the task in hand.
So I am kindly requesting that you take some time and make something better than <a class="postlink" href="https://www.aspnetzero.com/Documents/Developing-Step-By-Step-MPA">https://www.aspnetzero.com/Documents/De ... y-Step-MPA</a>
My opinion is that we take a Blog as an example and try to cover: Blog with Posts Post with many Tags Tag with many posts Comments (this way we cover one to many and many to many maybe one to one relationships)
with entity change event or domain events - post edited notify via email moderators background job if post date is > than 1-month archive post some notifications like subscribe to new posts of the blog etc.
I hope I am not asking too much but I rather find this to be more appropriate and will have great business value to your products.
At least please update the PhoneBook sample to cover entity change events and Domain events and maybe notification subscriptions.
Thank you in advance! Best Regards
1 Answer(s)
-
0
Hi,
Thank you very much for your comments and suggestion.
One problem with such a huge sample & documentation, it will be too complex for a sample. That's why most frameworks has only introduction level sample projects and dedicated tutorials/documentation for each feature. For example, we have already documentation for domain events, blog posts, notifications and so on. For a good example, this is almost an identical example code for 'archive post background job': <a class="postlink" href="http://www.aspnetboilerplate.com/Pages/Documents/Background-Jobs-And-Workers#create-a-background-worker">http://www.aspnetboilerplate.com/Pages/ ... und-worker</a> For nested relations, ABP uses EF and you can find good documents on the web. There is no special behaviour for AspNet Zero. We don't want to make a step by step document too long (it's already very long).
One good thing about AspNet Zero is it comes with full source code. So, you can take source code as example beside documentation.
This was my explanation for the current situation. However, we will take your feedback as a valuable comment. We will enhance documentation and samples. We are also thinking to create some video tutorials.
Thanks a lot. Have a nice day.
