docs/en/Community-Articles/2020-09-18-abp-framework--abp-commercial-32-rc-with-the-new-blazor-ui-/post.md
We are extremely excited today to release the ABP Framework Release Candidate (and the ABP Commercial, as always). This release includes an early preview version of the Blazor UI for the ABP.IO Platform.
While the Blazor UI should be considered as experimental for now, it is possible to start to develop your application today.
Currently, implemented some important framework features;
ISettingProvider, IFeatureChecker, ICurrentUser...Also, the standard .net services are already available, like caching, logging, validation and much more. Since the ABP Framework has layered itself, all the non-MVC UI related features are already usable for the Blazor UI.
Some modules have been implemented;
We've selected the Blazorise as a fundamental UI library for the Blazor UI. It already supports different HTML/CSS frameworks (like Bootstrap, Bulma, Ant Design...) and significantly increases the developer productivity.
We also have good news: Mladen Macanović, the creator of the Blazorise, is joining to the core ABP Framework team in the next weeks. We are excited to work with him to bring the power of these two successful projects together.
We've updated the web application development tutorial for the Blazor UI. You can start to develop applications today! The source code of the BookStore application developed with this tutorial is here.
If you want to try the Blazor UI today, follow the instructions below.
Install the latest ABP CLI preview version:
dotnet tool update Volo.Abp.Cli -g --version 3.2.0-rc.2
Then you can create a new solution using the abp new command:
abp new AbpBlazorDemo -u blazor --preview
Also, specify the -t app-pro parameter if you are an ABP Commercial user.
See the ABP CLI documentation for the additional options, like MongoDB database or separated authentication server.
Open the generated solution using the latest Visual Studio 2019. You will see a solution structure like the picture below:
DbMigrator project to create the database and seed the initial data.HttpApi.Host project for the server-side.Blazor project to start the Blazor UI.Use admin as the username and 1q2w3E* as the password to login to the application.
Here, a screenshot from the role management page of the Blazor UI:
Besides the Blazor UI, there are a lot of issues that have been closed with the milestone 3.2. I will highlight some of the major features and changes released with this version.
MongoDB integration now supports multi-document transactions that comes with the MongoDB 4.x.
We've disabled transactions for solutions use the MongoDB, inside the YourProjectMongoDbModule.cs file in the MongoDB project. If your MongoDB server supports transactions, you should manually enable it in this class:
Configure<AbpUnitOfWorkDefaultOptions>(options =>
{
options.TransactionBehavior = UnitOfWorkTransactionBehavior.Auto;
});
Or you can delete this code since this is already the default behavior.
If you are upgrading an existing solution and your MongoDB server doesn't support transactions, please disable it:
Configure<AbpUnitOfWorkDefaultOptions>(options =>
{
options.TransactionBehavior = UnitOfWorkTransactionBehavior.Disabled;
});
See the Unit Of Work document to learn more about UOW and transactions.
Also, add this file into your MongoDB project (remember to change MongoDbMyProjectNameDbSchemaMigrator and IMyProjectNameDbSchemaMigrator with your own project name).
Transactions are also disabled for automated integration tests coming with the application startup template, since the Mongo2Go library (we use in the test projects) has a problem with the transactions. We've sent a Pull Request to fix it and will enable the transactions again when they merge & release it.
If you are upgrading an existing solution and using MongoDB, please disable transactions for the test projects just as described above.
ABP Framework's distributed event system has been integrated to RabbitMQ before. By the version 3.2, it has a Kafka integration package, named Volo.Abp.EventBus.Kafka.
See the Kafka integration documentation to learn how to install and configure it.
ABP Feature System allows you to define features in your application. Then you can enable/disable a feature dynamically on the runtime. It is generally used in a multi-tenant system to restrict features for tenants, so you can charge extra money for some features in a SaaS application.
In some cases, you may want to use the same features in the host side (host is you as you are managing the tenants). For this case, we've added a "Manage Host Features" button to the Tenant Management page so you can open a modal dialog to select the features for the host side.
ABP Framework provides a system to dynamically create C# proxies to consume HTTP APIs from your client applications. AbpHttpClientBuilderOptions is a new option class to configure the HttpClients used by the proxy system.
Example: Use the Polly library to retry up to 3 times for a failed HTTP request
public override void PreConfigureServices(ServiceConfigurationContext context)
{
PreConfigure<AbpHttpClientBuilderOptions>(options =>
{
options.ProxyClientBuildActions.Add((remoteServiceName, clientBuilder) =>
{
clientBuilder.AddTransientHttpErrorPolicy(policyBuilder =>
policyBuilder.WaitAndRetryAsync(
3,
i => TimeSpan.FromSeconds(Math.Pow(2, i))
)
);
});
});
}
See the issue #5304 for the details.
We are using mono repository approach and the abp repository has tens of solutions and hundreds of projects (the framework, modules, tooling, templates...) with all of them are referencing to each other.
It gets a significant time to build the whole repository for every Git push. To optimize this process, we've created the abp build command in the ABP CLI:
abp build
We will use this command to build the abp repository or a solution inside it. However, it is available to everyone in case of need.
Most of the people will not need it. If you need it, see the ABP CLI document to learn all the details and options.
DynamicRangeAttribute that can be used to determine the range values on runtime, just like the DynamicStringLengthAttribute was introduced before.--skip-cli-version-check option to ABP CLI to improve the performance by bypassing the online version check.IProfileManagementPageContributor interface and register it using the ProfileManagementPageOptions class.And a lot of minor improvements and bug fixes. You can see the milestone 3.2 for all issues & PRs closed with this version.
The new profile picture management feature uses the BLOB storing system, so it needs a Storage Provider. The new startup template comes with the Database BLOB Provider pre-installed. You can change it if you want to use another BLOB provider (like Azure, AWS or a simple file system).
Existing solutions must configure a BLOB provider after upgrading to the version 3.2. Follow the BLOB Storing document to configure the provider yourself.
The experimental Blazor UI is also available for the ABP Commercial. The Lepton Theme hasn't been implemented with this initial preview, however we are working on it with the highest priority.
You can use the ABP Suite or the following ABP CLI command to create a new solution with the Blazor UI:
abp new AbpBlazorDemo -u blazor -t app-pro --preview
Please try it and provide feedback to us. Thanks in advance.
See the instructions in the Get started with the Blazor UI section above to properly create and run your application.
Angular UI for the File Management module is available with version 3.2. You can add it to your solution using the ABP Suite.
We've added profile picture management for the account module, so a user can select one of the options below for her profile picture;
Created features and settings to disable, enable or force to use 2FA on login for the tenants and users.
You can use the following command to upgrade the ABP Suite to the latest preview version:
abp suite update --preview
ABP Community web site is constantly being improved and new articles are added. We will add "commenting" and "rating" features to the articles soon to increase the interactivity between the people.
If you have something to share with the ABP community or want to follow the project progress, please check the community.abp.io!
We are silently working on a project, named CMS Kit, for a few months. CMS Kit is a set of reusable CMS (Content Management System) components based on the ABP Framework. Some of the components currently being developed:
There are more planned components like articles, tags, votes, favorites, portfolios, image galleries, FAQs... etc. We will document and deploy these components when they get matured and ready to use. Some of them will be open source & free while some of them are paid (included in the ABP Commercial license).
Please try the ABP Framework 3.2.0 RC and provide feedback to help us to release a more stable version. The planned release date for the 3.2.0 final version is October 01.