I meant to say, RAD Tool v2.2.1.1 - which is the new version released today.
Seems to work with RAD Tool 2.1.1.1.
Here is my TestEntity1:
This time the RAD tool changed\added 39 files.
Thanks for getting this fixed - at least for me. I know others will need to retry as well.
Yes, I will start working on it now and report back as soon as I know.
Don't know if this is helpful or not, but here is the list of files that got added\changed by Rad Tool 2.2.1 when generating a new entity:
I have been trying to get 8.5.0 Angular\Core and RAD Tool working together for the last two days (but still has problems that are documented in another question).
Just FYI, I HAVE been able to get 8.5.0 WITHOUT the RAD Tool to work. What I did differently than Javier was I did not run "yarn upgrade". With just "yarn" and then "npm start" it works for me.
One time when I was trying to get it working WITH the RAD Tool, I ran a "yarn upgrade". When I did that I got similar bootstrap errors to the ones Javier shows above.
Ok, I gave it another try and got the same results. Here is the sequence of events:
<br> <br> In the master branch, went through the normal steps from the Getting Started documentation (connection strings, update-database, build and run AspNetCore, yarn, nom start).
Everything runs that way:
<br> Created a new branch (TestNewEntity1) and ran the RAD Tool v2.2.1:
Generation completed without any errors:
<br> Built and ran the AspNetCore Host project.
Found my new entity in the API:
Ran nswag\refresh.bat:
Ran npm start and got these results:
<br> <br>
I have the same problem on the EPPlus with the RAD Tool in VS 2019 and Angular\Core 8.4.
I have not tried changing the AspNetZeroRadTool/config.json ProjectVersion setting yet.
Also, I have not tried building the Angular solution yet. I am guessing I will have the problem noted above with it.
This is also holding up our work on our project. Please let us know when you think this will be fixed.
Ok, at least I know that it is something that can be used by customers. Abp has so many classes and components and the documentation sometimes says "do this, but don't do that", that I am reluctant to use a component, without asking first, that is not found in the documentation.
Actually, I am going to close this question and ask about TenantCache in another question with a more accurate subject in the heading.
I guess I was looking more for some information on what the TenantCache is all about and its intended use (or non-use) by AspNetZero customers.
