Activities of "carl.hallqvist"

Hi,

Yes I can confirm that a valid certificate is present. Attaching screenshot. Thanks.

Thanks,

Thanks! I almost got it working with minimal changes. But I got this error at the blazer WASM load after using TLS:

• ABP Framework version: v9.X
• UI Type: Blazor WASM
• Database System: EF Core SQL Server
• Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
• Exception message and full stack trace:
• Steps to reproduce the issue:

In the ABP 7 we successfully made deployments in public cloud (DigitalOcean) using the generated Helm charts. We modified the values.yaml file and configured the domain names, with TLS certificates using Certmanager and Lets Encrypt.

Now, the Helm charts looking totally different and seems to be used for local deployment?

Can you please give short instructions how to deploy on public cloud?

Thanks

• ABP Framework version: v8.3.1
• UI Type: Blazor WASM
• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes
• Steps to reproduce the issue:

We have a number of services, e.g., DocumentService, InvoiceService and CustomerService

InvoiceService do API calls to CustomerService and DocumentService. CustomerService do API calls to InvoiceService.

We have tried to create a new class library and generate all client proxies in there. But the generated classes contain includes to the specific project. That means that it will be circular references?

Can you please guide us how to deal with the client proxies when two services do requests to each other?

Thanks

Never mind.. configuration issues..

"Customer": {
        "ClusterId": "Customer",
        "Match": {
          "Path": "/api/customer/{**catch-all}"
        }
      },
      "CustomerSwagger": {
        "ClusterId": "Customer",
        "Match": {
          "Path": "/swagger-json/Customer/swagger/v1/swagger.json"
        },
        "Transforms": [
          {
            "PathRemovePrefix": "/swagger-json/Ticket"
          }
        ]
      }

• ABP Framework version: v8.3.2
• UI Type: Blazor WASM
• Database System: EF Core SQL Server
• Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
• Exception message and full stack trace:
• Steps to reproduce the issue:

Using Microservice template and got this in when trying out an endpoint in a microservice. I am using the auto controller feature, so I have not defined any controllers.

[22:50:26 ERR] An unhandled exception has occurred while executing the request. Microsoft.AspNetCore.Routing.Matching.AmbiguousMatchException: The request matched multiple endpoints. Matches:

Customer Ticket at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ReportAmbiguity(Span1 candidateState) at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.ProcessFinalCandidates(HttpContext httpContext, Span1 candidateState) at Microsoft.AspNetCore.Routing.Matching.DefaultEndpointSelector.Select(HttpContext httpContext, Span`1 candidateState) at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.MatchAsync(HttpContext httpContext) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.Invoke(HttpContext context, ICorsPolicyProvider corsPolicyProvider) at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.ReflectionMiddlewareBinder.<>c__DisplayClass6_0.

Thanks! It worked with all services started.

Thanks,

We did some progress with that information. However, for some reason auth-server did not succeed to authorize admin@abp.io with password 1q2w3E* .

I did all database migrations (administration, audit-logging, identity and saas) but no success. Not even the log in auth-server indicates some error. Any ideas?

Best rregards.

• Database System: EF Core (SQL Server)
• Tiered (for MVC) or Auth Server Separated (for Angular): yes/no
• Exception message and full stack trace:
• Steps to reproduce the issue:

We have managed to get some sort of Hello World working with Blazor, but without any connection to the endpoints in our services.

Our plan was to try migrating the 7.3 project to 8.3.1, but we've had problems with it despite support.

Anyway, we don't quite understand where to place all the projects, and we would need a Hello World that includes the following:

1. A domain class / entity
2. An EF Core repository for the domain
3. An app service
4. A controller with working Swagger
5. Unit tests for the entity, repository, app service, and controller

This would be incredibly valuable. This is how we got started with ABP 6 and 7, as you had good documentation for a BookStore and tutorial, and with that knowledge from the ABP Framework, it was easy to start with microservice architecture.

I hope you can provide something like this, because we've completely lost the knowledge we had from version 7 now that we've started with 8.

Best regards.

Thanks,

It seems to work. However, the migration from < 8.2 to 8.2 is not very straightforward. Think it need some more documentation, the templates that was created for ABP 7 was a much easier.