Activities of "carl.hallqvist"

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.

Sure, here is the structure (creating a new ms template, then using ABP Studio to generate the customer microservice).

Edit: Updated screenshot

I am not sure where to place the ABP 7 projects:

services/customer/src/GeoTicket.CustomerService.Domain, services/customer/src/GeoTicket.CustomerService.Domain, services/customer/src/GeoTicket.CustomerService.Domain.Shared, services/customer/src/GeoTicket.CustomerService.Application, services/customer/src/GeoTicket.CustomerService.Application.Contracts, services/customer/src/GeoTicket.CustomerService.HttpApi, services/customer/src/GeoTicket.CustomerService.HttpApi.Client, services/customer/src/GeoTicket.CustomerService.HttpApi.Host

in the new ABP 8.3 structure. Please help me map those projects to the new directories / projects in the screenshot.

Thanks :-)

Thank you,

But does this mean that I shouldn’t partition out Blazor code into the different microservices (as in ABP 7), but rather put all the Blazor code under apps/blazor/ProjectName.Blazor and apps/blazor/ProjectName.Blazor.Client?

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

We have previously used ABP 7, but now we created an ABP 8.3 microservice template, and it looked different.

Specifically, the Blazor WASM application was missing when adding a new microservice according to: https://abp.io/docs/latest/solution-templates/microservice/adding-new-microservices#adding-a-new-microservice

How do you add a Blazor project in an added microservice?

Additionally, there are two projects in the /apps/blazor directory, ProjectName.Blazor.Client and ProjectName.Blazor. How does the Blazor project in the microservice appends as dependency project in /apps/blazor (like it did in ABP 7)?

Thank you in advance for your help.

Thanks,

I thought that you used the base to build inside container, and then copy that build into each app / service. But now I understand that that you build on host first.

Thanks, problem solved :-)

Sure,

I did not get the latest template (8.3.1) to work either. Same problem, no Blazor WASM.

Can you please give me the commands from installing correct ABP CLI version, to create a new template, and working Docker commands ?

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

Hi,

I struggling to get a containerized Blazor WASM Docker container to work. I have managed to get the other things to work in Kubernetes.

However, I am not sure how to deal with the different Dockerfile.azure, Dockerfile.base and Dockerfile.local , is there any reason to not just have one Dockerfile.base and a regular Dockerfile?

Can you please give me a working example of Dockerfile.base and a Dockerfile which create a Blazor WASM container image? The generated ones from 8.2.3 only create an empty nginx container as far as I can understand.

Thanks

Thanks, I got you and seems reasonable.

Hi,

Yes you can.

But I recommend you create a shared project

Thanks, I understand but not the reason. Can you tell me please? :-)

Ok, but why it is not possible to reference service a in service b? It is just the front-end client I mean. Bad practice or any other technical issues? In some projects I have seen only one big Blazor project, that communicate with the gateway. ABP MicroService have one top Blazor app, referencing to other Blazor project in the different services.