Hi @maberry
- When compared to ABP Suite, generated code in OnModelCreating works as designed. ABP Suite and also ABP Framework has a different approach here, that's why its generated code is different.
- Duplicate of City entity in OnModelCreating is not what we expect. Could you share steps to reproduce this problem ?
- Making modification on generated entities to move some fields to separate tables (like creating a City table instead of City field in Location entity) shouldn't be done using Power Tools. Power Tools is designed to be used mostly for first time usage. You can ofcourse make modifications for adding primary (text, int etc...) fields to existing entities. However, for moving a field to a new table, it would be better to make changes on the generated entity using Visual Studio.
I completely understand the approaches are different, but doesnt really answer the question of why Power Tools does not generate code OnModelCreating. ABP Suite is not the only code generator that puts more information in OnModelCreating. Not doing so causing all kinds of warnings in Visual Studio for null referrences, etc when building a project. Your answer indicates that it is working as expected. My question again - are you able to provide rationale for this behavior considering it causes errors and goes against convention?
Steps to reproduce duplication of entities in OnModelCreating - This happens EVERY time I regenerate an entity using Power Tools. That is the only step.
Am I understanding correctly that an appropriate use of Power Tools would be to regenerate entities for the purpose of adding fields, relationships, etc; however, removing fields, relationships, etc is not an appropriate use of the entension? If that is the case, it would seem like that information should most certainly be included in the documentation. I can not be the only person who wasted hours attempting to fix broken code after trying to remove a field. Just a thought.
Hi @maberry
Sorry for our late reply. AspNet Zero Power Tools generates the pages in a specific way. The scenario you are trying to develop is something totally different. Converting Power Tools generated source code to Metronic wizard is not something we can provide support for.
However, you can develop this page from scratch and I think it will be easier. To learn basics of ASP.NET Zero's Angular version, I suggest you to first follow https://docs.aspnetzero.com/en/aspnet-core-angular/latest/Developing-Step-By-Step-Angular-Introduction if you haven't.
Then, you can use correct servies for filling dropdowns. I hope this helps you to get started with AspNet Zero.
I am not asking for asking for assistance converting Power Tools generated source code to the Metronic wizard layout.
What I need to know is how to implement a cascading dropdown list within the aspnetzero framework. The "typical" way of doing it will not work because of how the aspnetzero code is structured.
I am not sure why you offerred the link you did. It does not appear to offer a cascading dropdown list. Furthermore, I have search all of the sample applications I can find using both aspnetzero and ABP. Several people have asked the same question over the years (such as here: https://support.aspnetzero.com/QA/Questions/3292/Cascading-Dropdownlist). Unfortunately, the support representative sent the information via email rather than provide assistance through the forum.
Three days and no response from customer support. This does not bode well considering I just getting into aspnetzero. Good thing I am still within the 30 day window.
