Finally, ABP has a SPA UI option with the latest Angular framework. Angular integration was not simply creating a startup template.
- Created a base infrastructure to handle ABP's modularity, theming and some other features. This infrastructure has been deployed as NPM packages.
- Created Angular UI packages for the modules like account, identity and tenant-management.
- Created a minimal startup template that authenticates using IdentityServer and uses the ASP.NET Core backend. This template uses the packages mentioned above.
- Worked on the ABP CLI and the download page to be able to generate projects with the new UI option.
- Created a tutorial to jump start with the new UI option.
We've created the template, document and infrastructure based on the latest Angular tools and trends:
- Uses NgBootstrap and PrimeNG as the UI component libraries. You can use your favorite library, no problem, but pre-built modules work with these libraries.
- Uses NGXS as the state management library.
Angular was the first SPA UI option, but it is not the last. After v1.0 release, we will start to work on a second UI option. Not decided yet, but candidates are Blazor, React and Vue.js. Waiting your feedback. You can thumb up using the following issues:
Widget system allows to define and reuse widgets for ASP.NET Core MVC applications. Widgets may have their own script and style resources and dependencies to 3rd-party libraries which are managed by the ABP framework.
We've solved many bugs and worked on existing features based on the community feedback. See the v0.19 milestone for all the closed issues.
We had decided to wait for ASP.NET Core 3.0 final release. Microsoft has announced to released it at .NET Conf, between 23-25 September.
We have planned to finalize our work and move to ASP.NET Core 3.0 (with preview or RC) before its release. Once Microsoft releases it, we will immediately start to upgrade and test with the final release.
So, you can expect ABP v1.0 to be released in the first half of the October. We are very excited and working hard on it.
You can follow the progress from the GitHub milestones.
We will not add major features until v1.0.