Starts in:
2 DAYS
15 HRS
21 MIN
46 SEC
Starts in:
2 D
15 H
21 M
46 S

Activities of "Leonardo.Willrich"

It worked. Thank you for your catch!

I've deleted all publish folder, have restarted Visual Studio 2022, and like magic, it seems that it is getting the right abp.js. I'll publish and will see it if is working.

That is what I know too. But, wwwroot and node_modules are exactly the same, only the one created in the publish folder is different. That is weird.

Ok, indeed, the published and my local wwwroot are different. Where is abp.js copied when publishing? It should be the same.

Ok, thank you for the reminder. Unfortunately, it is still not working. I'll try to copy my local abp.js just to be sure.

Ok, have run "abp install-libs" and I'm publishing again. I always publish in a local folder and copy the files to IIS.

That is my package.json:

{ "version": "1.0.0", "name": "my-app", "private": true, "dependencies": { "@volo/abp.aspnetcore.mvc.ui.theme.lepton": "^7.2.1", "@volo/account": "~7.2.1" } }

Hi,

That is weird, why when running locally it works and when published it doesn't. How should I update in package.json? It is exactly equal to the fresh new template.

Maliming,

I have got a fresh new template, BlazorWASM 7.2.1, I have published and it is working. In the other project that I've mentioned it wasn't working, it is actually working. It is only this project, sbc.dev, that is not working. Let me know if you want me to send all project if required.

Hi Maliming,

It didn't change, I'm still getting the same issue.

Showing 1 to 10 of 145 entries
Made with ❤️ on ABP v9.1.0-preview. Updated on November 20, 2024, 13:06