Updating my existing Blazor project, it updates Volo packages but not Blazorise package, so, it becames incompatible:
Error: Severity Code Description Project File Line Suppression State Error NU1605 Detected package downgrade: Blazorise.Components from 0.9.3.3 to 0.9.3-preview6. Reference the package directly from the project to select a different version.
TVD_Holdings_Ltd.AvalancheOCP.Blazor -> Volo.Abp.LanguageManagement.Blazor 4.3.0-rc.1 -> Volo.Abp.AspNetCore.Components.Web.Theming 4.3.0-rc.1 -> Volo.Abp.BlazoriseUI 4.3.0-rc.1 -> Blazorise.Components (>= 0.9.3.3)
TVD_Holdings_Ltd.AvalancheOCP.Blazor -> Blazorise.Components (>= 0.9.3-preview6) TVD_Holdings_Ltd.AvalancheOCP.Blazor D:\Source\AvalancheOCPLatest\src\TVD_Holdings_Ltd.AvalancheOCP.Blazor\TVD_Holdings_Ltd.AvalancheOCP.Blazor.csproj 1
yes, ABP CLI and Suite updates only ABP & Volo NuGet packages and related NPM packages. It doesn't update non ABP packages. Updating all the other packages can have unwanted consequences. therefore you should manually update Blazorise.
the original templates are in the Volo.Abp.Commercial.SuiteTemplates.dll
but when you modify a template it's stored in your solution folder so it's not only in your computer but also being committed to your souce control system. so your team also uses the same templates. and it's solution level.
If we used lepton material theme in the application. Does it support ie. material themes directly ?
sorry, didn't get this question!
https://support.abp.io/QA/Questions/1077/Testing-Overridden-AppService#answer-1bbd38f2-5f8c-36ad-6eeb-39fb70a23930
You are not granted permission to use the module 'Volo.Abp.Suite-v4.2.1.0'.
login via ABP CLI to fix this: https://docs.abp.io/en/abp/latest/CLI#login
you have 2 organizations. if you cannot login, you have to specify your active organization like below
abp login shobhit --organization Projile Corporation
2- Cannot run the angular app
When this problem occurs?
sorry your problem is related to an active issue on the Oracle provider. This problem is not related to ABP. When Oracle fixes, we'll update our package as well.
See https://github.com/abpframework/abp/issues/8210
Oracle official package should be working without any issues with the latest preview version. We have updated the package. But please try it with the 4.3.0-rc2 which will be published on friday (2021-04-09).
You'll use this command:
abp new Acme.BookStore -t app-pro --database-management-system oracle -csf --preview
@hitaspdotnet microservice project creation has been fixed.
@ilitzy your template pls? blazor, mvc, angular.
@murat.yuceer 4.3 RC deployment is still ongoing so some packages maybe still in publish phase.
My previous code will also not work in your case. I'll explain the structure, why it doesn't work as you expect and what you can do for a solution;
The below code executes InsertAsync
method with saveChanges=false
. This means the entity org
will be set as inserted record to the EF Core tracking system. At this point no real insert operation is done. So you'll leave the method without getting any exception because still no database operations has been done. Right after you leave the method, the framework calls SaveChanges
method of the EF Core's DbContext class. It discovers any changes to the entity instances and applies to the database. And you get exception at this point. But you already left the try-catch block and HTTP-500: An internal error occured
exception will be thrown to the UI.
public async Task AddOrganizationAsync(Organization org)
{
try
{
await _organizationRepository.InsertAsync(org, false);
}
catch (DbUpdateException ex) {
throw new MyCustomException(ex.Message, "2601");
}
}
If you want to catch the exception in a try-catch block you need to save the changes before leaving the try-catch block.
If you have several database operations you can call SaveChanges
one time when you finish all the database operations.
public async Task AddOrganizationAsync(Organization org)
{
try
{
await _organizationRepository.InsertAsync(org, false);
await _organizationMemberRepository.InsertAsync(org.Members, false);
await _organizationInvoices.UpdateAsync(org.Invoices, false);
await _organizationStatistics.DeleteAsync(org.DeletedSomeId);
//and other DB operations...
//apply changes to the database, you can handle exception at this point
await UnitOfWorkManager.Current.SaveChangesAsync();
}
catch (DbUpdateException ex) {
throw new MyCustomException(ex.Message, "2601");
}
}
Documents: