ABP Framework & ABP Commercial 3.3 Final Have Been Released
ABP Framework & ABP Commercial 3.3.0 have been released today.
Since all the new features are already explained in details with the 3.3 RC Announcement Post, I will not repeat all the details again. Please read the RC post for new feature and changes you may need to do for your solution while upgrading to the version 3.3.
Creating New Solutions
You can create a new solution with the ABP Framework version 3.3 by either using the abp new
command or using the direct download tab on the get started page.
See the getting started document for details.
How to Upgrade an Existing Solution
Install/Update the ABP CLI
First of all, install the ABP CLI or upgrade to the latest version.
If you haven't installed yet:
dotnet tool install -g Volo.Abp.Cli
To update an existing installation:
dotnet tool update -g Volo.Abp.Cli
ABP UPDATE Command
ABP CLI provides a handy command to update all the ABP related NuGet and NPM packages in your solution with a single command:
abp update
Run this command in the root folder of your solution. After the update command, check the RC blog post to learn if you need to make any changes in your solution.
You may want to see the new upgrading document.
About the Next Version: 4.0
The next version will be 4.0 and it will be mostly related to completing the Blazor UI features and upgrading the ABP Framework & ecosystem to the .NET 5.0.
The goal is to complete the version 4.0 with a stable Blazor UI with the fundamental features implemented and publish it just after the Microsoft lunches .NET 5 in this November. The planned 4.0 preview release date is November 11th.
Comments
Sacombank App 229 weeks ago
There many version has been released, so example when we use version 3.3 to develop my portal then when version 4.4 released => we using abp update command to upgrade ABP Commercial version, is that ok? all function we done is working normally or we need to rework? Thanks!
Halil İbrahim Kalkan 229 weeks ago
Hi, abp update command updates NuGet & NPM packages. If there are breaking changes between the versions, you should handle them manually. For example, ABP v4.0 will have breaking changes due to .NET 5 and IdentityServer 4 upgrades. We document the breaking changes and announce in every release post.
Sacombank App 229 weeks ago
Ok tks hikalkan
mani121 229 weeks ago
From the background job can't able to access tenant based records. I have tenant id but in background job can't able to get or access the records using repository as well dbcontext also.
Halil İbrahim Kalkan 229 weeks ago
If you have TenantId, then you can use ICurrentTenant.Change to switch to the tenant's context. See the doc: https://docs.abp.io/en/abp/latest/Multi-Tenancy#change-the-current-tenant
mani121 229 weeks ago
thanks @hikalkan
mani121 229 weeks ago
This will work for IEmailSender also. Because I'm using AbpSettings for saving SMTP credential. I stored credential like ISettingManager -> SetForCurrentTenantAsync. I'm using IEmailSender -> QueueAsync background job.