Activities of "alper"

@jason.smith if you think this is a subject of the Nginx reverse proxy problem, you can keep on discussing it here. If you think it's a separate issue, it'd be better to discuss it in a different thread. If you are worried about your question credits, I already increased your question credits by 1.

@jason.smith does the same URL work in the MVC application?

@rbarbosa I think you should ask in the Angular official repo. But I guess you have a custom link that starts with https://localhost/ . Your links should start with /

@hoatv2 , I need the Suite logs. You can find it in %UserProfile%\.abp\suite\logs

@gvnuysal yes, I know the reason.

The files and folders in it will be overwritten when proxy generation is run again. https://github.com/abpframework/abp/blob/dev/npm/ng-packs/packages/tenant-management/src/lib/proxy/README.md

@DanielAndreasen

ABP suite is however still showing my project as having version 3.1.0:

we've already fixed this issue in the next version ;)

@DanielAndreasen , @gvnuysal

To upgrade from v3.1.0 to v3.3.0 follow this => https://support.abp.io/QA/Questions/529/ABP-Upgrade-from-310-to-330#answer-0d9caf26-c6bd-b4f8-30cd-39f8a0144ec0

I migrated a 3.1.0 project to 3.3.0. Didn't get any Cannot read the template XXXX error. Close the Visual Studio and delete all bin&obj folders. Then rebuild your solution to restore the latest 3.3.0 packages. The templates are in the Volo.Abp.Commercial.SuiteTemplates library. Ensure that you have Volo.Abp.Commercial.SuiteTemplates v3.3.0 in the Domain.Shared project.

Upgrade all Microsoft.Extensions.FileProviders.Embedded packages from 3.1.6 to 3.1.8.

To do this find/replace all the below line

Include="Microsoft.Extensions.FileProviders.Embedded" Version="3.1.6"

with this line

Include="Microsoft.Extensions.FileProviders.Embedded" Version="3.1.8"

There are 2 namespace changes

1. Add using Volo.Saas.Editions; to SaasDataSeedContributor.cs
2. Add using Volo.Saas.Tenants; to XXXDbMigrationService.cs

You'll get the following error: No BLOB Storage provider was registered! At least one provider must be registered to be able to use the Blog Storing System.

To fix this;

Add the below package to the project XXX.EntityFrameworkCore:

<PackageReference Include="Volo.Abp.BlobStoring.Database.EntityFrameworkCore" Version="3.3.0" />

Add the below configuration to the ConfigureServices of your XXXWebModule.cs

Configure<AbpBlobStoringOptions>(options =>
{
    options.Containers.ConfigureDefault(container =>
    {
        container.UseDatabase();
    });
});

How to upgrade my ABP project from v3.1.0 to v3.3.0?

@DanielAndreasen can you check whether the ABP framework references are updated or not? I want to understand the issue