Yes, I have updated abp suite and created a new project.
There is the fix for advanced filters that were not generated before, but in abp suite there is no check box to choose which fields to use.Maybe I didn't explain myself well.
I expected to have the "Advanced Filter" checkbox in the field propertiesThanks for your patience
Oh you mean you want to have the advanced filter optionally generated (for all UI types)
Yes, like RadTool does on AspNetZero Thanks
Yes, I have updated abp suite and created a new project. There is the fix for advanced filters that were not generated before, but in abp suite there is no check box to choose which fields to use.
Maybe I didn't explain myself well. I expected to have the "Advanced Filter" checkbox in the field properties
Thanks for your patience
Add the features present in AspNetZero RadTool to Abp Suite as the section "Other" where we can set "Advanced Filter", "List in UI" and "Create and Update".
And, if possible, reduce the number of template files used by Abp Suite also giving the possibility to indicate the sub-path where to save the files as it could be done in AspNetZero RadTool.
Thanks,
Robertoyes this is on the roadmap , we'll implement it.
this feature is included in ABP v7.2 release.
@alper The Advanced Filter is still missing on the Blazor WASM UI template 7.4 rc2. When will it be released? Thanks
https://docs.abp.io/en/commercial/latest/startup-templates/application/deployment-iis?UI=Blazor&DB=EF&Tiered=No
Write the guide for deployment on IIS also indicating how to publish Blazor WASM (frontend and backend project) from VS2022 with different environments (DEVELOP/STAGING/PRODUCTION)
Thanks
I'll try, but I think I'll get a warning like https://learn.microsoft.com/en-us/dotnet/csharp/misc/cs0436?f1url=%3FappId%3Droslyn%26k%3Dk(CS0436)
Thanks
That is, I should clone ABP (framework) with the indicated PR and then from the ABP Commercial Solution remove the ABP packages and point directly to the local version DLLs built by the PR. Is it correct?
The ABP Commercial PRO modules, of which I don't have the sources, that point to ABP's nuget packages will have no problems?
Thanks for your answer
Hi @maliming but how can I use a PR of ABP Framework within my Abp Commercial Solution in which ABP is referenced via nuget package?
We added an extension method to sign out after the access token expired.
Blazor Server https://github.com/abpframework/abp/pull/15876
Blazor wasm https://github.com/abpframework/abp/pull/16504
You can copy the code if you use lower version of abp.
Hi @maliming, but https://github.com/abpframework/abp/pull/16504 is still open. In which version of Abp Blazor WASM was it fixed?
Thanks
I think this is a common problem for all. Blazorise now requires its own license for use in commercial software. This cannot be ignored. Blazorise license should be included with Abp Commercial.
Now you can read this post https://support.abp.io/QA/Questions/5037/How-do-we-get-support-with-Blazorise#answer-3a0b3114-427d-f26e-4cc5-88ff791f3ff3
I would like to implement a webhook feature like ASP.NET Zero.
https://docs.aspnetzero.com/en/aspnet-core-mvc/latest/Features-Webhooks
You can implement this feature on the framework side > https://github.com/abpframework/abp We will be happy to see your PR.
I think @portx-dev was asking you to develop it as a feature of the Abp Commercial version :-)
The requested feature is already on the roadmap https://docs.abp.io/en/abp/latest/Road-Map from 2020 https://github.com/abpframework/abp/issues/4223