Hi, its Blazor Server not Wasm.
I really need this, because i need to publish that solution internally for further test as soons as possible. So when do you expect to update them ? can you provide me a working sample with blazor server or the etc/k8s folder ?
Hi @gterdem,
the added microservie also uses Blazor. Maybe you would like to check my solution remotly ?
Yes, this fixed it. Can you explain why ? Will it be replaced in the template or through abp-cli for future ?
No, sorry a page refresh wont change something. There error still persits. i did misunderstood you.
Yes this works fine. also cleared all cookies in browser. If i generate a product from blazor app menu the product is created fine.
but in swagger i receive the above error. Same swagger problem also with the other services.
"app.UseCors();" was missing in the NewServiceHttpApiHostModule in OnApplicationInitialization.
After adding it ,it works. Seems to be an issue in abp-cli.
Hi @gterdem,
yes indeed "app.UseCors();" was missing in the NewServiceHttpApiHostModule in OnApplicationInitialization. Seems to be an error in generation through abp-cli. but this did resolve it..
I thank you. I needed that fix. When will that be fixed in cli ?
I have the same error, please look here: https://support.abp.io/QA/Questions/3310/Howto-integrate-a-standard-template-pro-solution-as-new-service-in-a-microservice-solution
I did try to add my newservice to all appsettings, without success. i also did replace the port number of product-service with my new service in ocelot.json without success. so from my point liangshiwei advise didn't work for me
Hi,
till now i dont got any solution for this. Cors gives the error for the new service but i didn't any differerence to product service. The cors setting is exactly the same in appsettings.
I hope the support team will solve this for us. I need this fixed.
your document "https://docs.abp.io/en/commercial/latest/startup-templates/microservice/add-microservice" contain infos about the internal gateway and project reference which doesn't exist anymore, this one needs an update
if i try to follow you document how to change to mongodb. i receive a lot of errors in vs
The Port 44325 is port of the WebGateway, The Port 44472 is the port of my new microservice. I also receive this error on the PublicWebGateway which runs at Port 44353. Both Gateways are added to the new microservice appsettings Cors configuration per default. Also if i open the new microservice page in tye directly (https://localhost:44472) . it works fine but not if try to access it over an gateway. I did follow also the section about the gateways in your microservcice document any didn't find any difference.
I did reproduce it with these steps:
