Activities of "enisn"

Purging cache after deletion a tenant was shipped in v5.2.1.

There is a couple of ways to achieve that.

• You can create a controller that redirects like below https://github.com/abpframework/abp/blob/dev/modules/cms-kit/host/Volo.CmsKit.HttpApi.Host/Controllers/HomeController.cs#L10

• You can create a new page that handles the"/" path by beginning with @page "/" .

  You can check this out: https://docs.microsoft.com/en-us/aspnet/core/razor-pages/razor-pages-conventions?view=aspnetcore-6.0

• AspNetCore default routing pattern is {controller=Home}/{action=Index}/{id?}. You can change that pattern via configuring routing. Check this out: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/routing?view=aspnetcore-6.0#route-templates

Hi @krushnakant

I'm not sure what you mean by EF API. You should encapsulate your parameters with DTO and you can generate queries with those parameters in the repository.

It's not recommended that expose entities or database queries directly to the client.

• https://docs.abp.io/en/abp/5.2/Best-Practices/Application-Services#getting-a-list-of-entities

If you mean passing MaxResultCount and SkipCount parameters, you can send them manually.

this.authorService.getList({ "maxResultCount": 2, "skipCount": 4 });

Then can you provide steps to reproduce?

Hi @cellero

It seems there are some missing sections in commercial documentation.

Can you try execute abp bundle command under the blazor project and then run it again? That should solve the issue.

Also your credit is refunded.

It is Blazor Server right? This happens in Blazor Server only. Can you try clearing the entire cache, local storage, and cookies for localhost domain, then restart the application and try again?

It might be happening because of web applications that ran on localhost before.

In the Gateway ocelot configuration, that pattern"/api/abp/{everything}" is proxying /api/abp/api-definition path to Administration Service.

That works fine while using static client proxies because they don't check that endpoint at runtime. If you go with dynamic client proxies, add the following mapping to OnApplicationInitialization method in your Gateway Module class.

app.MapWhen(
    ctx => ctx.Request.Path.ToString().StartsWith("/api/abp/api-definition") ||
           ctx.Request.Path.ToString().TrimEnd('/').Equals(""),
    app2 =>
    {
        app2.UseRouting();
        app2.UseConfiguredEndpoints();
    }
);

Make sure it is placed right before app.UseOcelot().Wait();

Hi isaac.yip@cpy.com.hk

Unfortunately, we couldn't reproduce this issue. Can you please share a sample project with this issue number (2963) to my email address?

enis.necipoglu@volosoft.com

Can you verify the t-generate-proxy.json file is updated and has those methods in it?

By the way, I can't reproduce this issue, can you send me an example project with the issue number (#2899)?

enis.necipoglu@volosoft.com

If you're working on localhost, please check your IdentityServerDataSeedContributor.cs class before running DbMigrator. That class is placed under IdentityServer folder under Domain project by default. All Clients are defined there and they're seeded to run your app properly at the initial state.

Make sure the following code block exits and blazor URL is configured properly in appsettings.json of DbMigrator project.

  var blazorClientId = configurationSection["MyProjectName_Blazor:ClientId"];
        if (!blazorClientId.IsNullOrWhiteSpace())
        {
            var blazorRootUrl = configurationSection["MyProjectName_Blazor:RootUrl"].TrimEnd('/');

            await CreateClientAsync(
                name: blazorClientId,
                scopes: commonScopes,
                grantTypes: new[] { "authorization_code" },
                secret: configurationSection["MyProjectName_Blazor:ClientSecret"]?.Sha256(),
                requireClientSecret: false,
                redirectUri: $"{blazorRootUrl}/authentication/login-callback",
                postLogoutRedirectUri: $"{blazorRootUrl}/authentication/logout-callback",
                corsOrigins: new[] { blazorRootUrl.RemovePostFix("/") }
            );
        }

After configuring everything well, run the DbMigrator once to seed client options.

Also, please check appsettings.json file under your HttpApi.Host project. There should be a section like that:

 "App": {
    "CorsOrigins": "https://*.yourproject.com"
  },

You can separate CorsOrigins with coma (,), make sure there is your blazor url.