Not sure if this is a bug or intentional but when creating a Blazor WASM in ABP Suite, it creates both a ProjectName.Blazor and a ProjectName.Blazor.Client project, ie just like if you create a Blazor WebApp project. This is different from the Visual Studio template which only creates a single project for Blazor WASM, and also unlike how it was before from what I remember (could be wrong). If you create a Blazor Server project, it will still only be a ProjectName.Blazor project.
So it seeems ABP Suite basically creates a WASM version of the Blazor WebApp, which you can also see by it containing .AddInteractiveWebAssemblyComponents(); etc.
It does seem to be working though, but not sure if this is intentional but it is at least different from the Blazor WASM template in Visual Studio?
In the new version, we switched to Blazor WebApp hosting logic. Yes your project will have both of projects (
.Blazorand.Blazor.Client) but its behavior is what you pick while creating. If you choose WASM, it'll work as blazor-wasm, if you choose server, it'll work as blazor-server. We just merged infrastructure of all blazor project-types. Still you can create an old template and upgrade it to use previous logic
Thanks for the info. I believe this is a good decision going forward as I would imagine that the WebApp will sooner or later replace the other two alternatives, or rather merge them into the WebApp setup.
This does mean however that the current documentation needs to be updated as it currently still assumes the old structure, like
https://docs.abp.io/en/commercial/latest/tutorials/book-store/part-2?UI=Blazor&DB=EF
"Create a Books Page It's time to create something visible and usable! Right click to the Pages folder under the Acme.BookStore.Blazor project and add a new razor component, named Books.razor:"
Which I assume would now be the .Client project rather (at least for WASM). Maybe you've already got that planned for when the actual release is as the documentation is probably still correct for pre WebApp support.
You can report all your ABP-related issues on this platform.
Other platforms are for open-source users. We read all these posts and take necessary actions.
PS: You can still use the following platforms to find a community-supported solution.
- https://github.com/abpframework/abp
- https://stackoverflow.com/questions/tagged/abp-framework
- https://discord.gg/abp
Thanks! Glad to hear. After all, we are in this together :)
I don't think that we are the only customers that would want a little more feedback in the commercial support forums. Does not really have to be all that much but just to know that someone from ABP is actually reading what we write and also if it leads to some kind of action and if so, what it is. Basically what GitHub Issues/Discussion offers. I also think that this would encourage ABP Commercial Customers to actually give feedback when you know that someone at ABP is really reading and using it. Which would be good for everyone I think. I know from my own experience/mistakes how easy it is to assume that everyone knows as much as you do yourself just because you happen to be in the loop yourself.
Have you ever considered actually setting up a GitHub alternative to these support forums? I would imagine that most of the ABP team is using GitHub all day long as well so it would be easier to have everything in one place. Or perhaps simply just allow commercial issues in the normal GitHub issues, as those seem to thrive with activity, even though I can understand there being some cons to that as well since the codebase there does not include the commercial features.
Thanks.
Is anyone from ABP actually following this thread?
Not sure if this is a bug or intentional but when creating a Blazor WASM in ABP Suite, it creates both a ProjectName.Blazor and a ProjectName.Blazor.Client project, ie just like if you create a Blazor WebApp project. This is different from the Visual Studio template which only creates a single project for Blazor WASM, and also unlike how it was before from what I remember (could be wrong). If you create a Blazor Server project, it will still only be a ProjectName.Blazor project.
So it seeems ABP Suite basically creates a WASM version of the Blazor WebApp, which you can also see by it containing .AddInteractiveWebAssemblyComponents(); etc.
It does seem to be working though, but not sure if this is intentional but it is at least different from the Blazor WASM template in Visual Studio?
When creating a new Blazor WASM in ABP Suite you get
Cannot change the connection string in /aspnet-core/etc/docker/appsettings.json. Error: After parsing a value an unexpected character was encountered: ". Path 'RemoteServices.AbpAccountPublic.BaseUrl', line 24, position 6.
(Default value for connection string and db used, ie no changes to what ABP Suite suggests)
Seems like this is being handled here now
https://github.com/abpframework/abp/issues/20078
Would be nice if there were a way to know this, I just happened to see this by luck as I don't normally scroll through every issue, is there a way to see GH issues related with support tickets here?
Where can I find more information about the ABP Personal Edition license?
Note sure if these are in anyway related to each other, maybe not but related areas
https://support.abp.io/QA/Questions/7323/BUG-Login-page-in-browser-does-not-redirect
hi
Does the abp suite meet your requirements?
The ABP Suite has been fantastic for generating components and has saved a lot of development time. However, I'm finding it challenging to enhance the UI to the level we desire. The suite's convenience has admittedly made me a bit lazy in this regard, so I’m reaching out for your guidance.
Could you recommend a UI framework that integrates smoothly with ABP and the Lepton Pro theme? We're looking for something that can help us achieve a more polished and modern look and save time too.
Thanks for your help!
We kind of came to the same conclusion for our project(s) resulting in that we mainly used ABP Suite for generation of non UI code to save some time but instead built the UI ourselves with something like DevExpress, Telerik etc. Especially with LOB applications where a powerful datagrip component is a requirement etc.
I am working with version 8.2.0-rc.5 (new Blazor Server project) and have the problem that I have to log in almost every time I start the application from Visual Studio, even if I select "Remember me". Sometimes the automatic login works, but only very rarely and I have not yet found out when this is the case.
Also, the background of the login page is purple instead of blue and after logging in, the dark theme is shortly displayed before it automatically switches to the system theme. I also have to click away the cookie message every time.
I didn't have these problems with version 8.1... Can anyone confirm this behavior?
Have not seen this problem with any of the RC versions of ABP Suite 8.2 I have tried (including RC5).