Activities of "improwise"

It's already done by MAUI but it seems WinUI3 has a problem with that Activate() method: https://github.com/microsoft/microsoft-ui-xaml/issues/7595

It brings too complex solutions,

It seems this one is good: https://stackoverflow.com/a/12758966/7200126 But still I recommend waiting WinUI3 to fix it. In our side we'll add another page when redirect uri scheme is different than http(s)

At least some confirmation to the user that authentication was successful goes a long way and should also be independent from redirects etc. ie quite easy to implement. As of now, it just looks like nothing happened unless you know what to look for.

Hi,

MAUI implements the default behaviour of OAuth login and redirects to browser to login. And browser redirect back to the application with a specific scheme like (yourapp://callback). By default it should open your application and bring it to the front. But I reproduced the same scenario as you said, it stays in the background but login operation is completed. Here is the 2 cases:

  • We can implement a new page after redirection to different schemes than http(s)://
  • We can implement the logic in the MAUI app that brings to the front itself on the desktop apps and use can recognize that the login operation is done.

Thanks.

Still waiting for a reply...

There seem to be a problem with at least the latest RC versions that ABP Suite hangs, at least "visually". Even when you have received the "new project created" web page popping up and "Done XXX" in the CLI, it still often looks like this for quite some time in ABP Suite

If you wait long enough, it usually wakes up and shows the "The ABP solution has been created. Do you want to create the database and seed the initial data?" dialog.

Overall it seems like the ABP Suite in 8.2 RC is much slower than the one in 8.1.

Still waiting for a reply here.

@enisn

This seems to work. Since there is a MainFooterComponent.razor file that isn't used, we updated that one with

@inherits Footer @attribute [ExposeServices(typeof(Footer))] @attribute [Dependency(ReplaceServices = true)]

which seems to work so far.

Thanks. Will give it a try.

  • ABP Framework version: 8.2 RC4 (but seems to be the same with non RC)
  • UI Type: MAUI Blazor

When you create a new MAUI Blazor solution in ABP Suite, you get this footer in the application

Have not been able to find anyway it can be removed / configured including the three buttons to the right and it also seems like the MainFooterComponent is ignored

<span class="copyright-text">@DateTime.Now.Year © MyProject</span>

Seems like this is something hard coded into the LeptonX them as they are visible on the demo site as well (where the About, Privacy and Contact buttons do nothing as well). For the free theme / ABP I could perhaps understand this but for solutions created with ABP Commercial / ABP Studio, I can't think of any customer wanting to do marketing for another company in their app. I would imagine you could download the source code for LeptonX and modify it, but that is of course something you should not need to do unless you really want to change the theme so I assume that isn't needed.

How can we get rid of this and why is it there to begin with?

Thanks.

(I think I have seen this in other non MAUI Blazor projects as well but as we are currently building a MAUI Blazor app, it is reported as such.)

One thing I would like personally is a notice that the ticket investigation has started, or even has been seen, on a post.

I've seen one ticket today that's over 9 days old without even initial feedback on it, just a chaser by the OP.

I've logged a P1 ticket for us today as we can't do any work with the feed out, but no idea if it's even been seen by the support team.

I agree 100% with this comment/request. My dev recently submitted a ticket and we followed up three times before finally receiving any acknowledgement that the ticket had even been read after 12 days. In general, ABP.io is marketed as an enterprise grade solution, and as such, commercial license holders should be provided with enterprise grade support. Project delays can be extremely costly, and the only thing worse than bad information, is no information at all. We received a response, however it did not address the issue fully, so we are continuing to struggle to get the project back on track. My suggestion is to recieve a real acknowledgement (not automated) within 24 hours of being submitted from the assigned support specialist. A full response should be furnished within 48-72 hours (or 2-3 business days).

I agree with this and also have a general feeling that the ABP Team just need to be more active in here. While I fully understand that users of the free open source version of ABP can't really make any demands, the ABP Commercial product is as you say marketed as an enterprise product and also comes with a quite substantial price (everything is relative of course) which at least to me means that our expectations also increase. I kind of feels that we are somewhere in between an actual enterprise product and a boilerplate one where you get a great start and lots of nice features, but then you are on you own.

I would also like to see a "support guide" that helps us understand what to put where in terms of questions, bugs, problems etc, as I find it confusing to separate this forum, different threads at this forum from each other, email support, GitHub issues etc. It is also a bit confusing sometimes to know what is "commercial" and what isn't when you run into issues. It also becomes more a bit more challenging when using something like ABP Suite to generate a solution, which would mean that what we get isn't exactly the same as someone using the free version would get, and this makes me unsure what I should report as GitHub Issues and what to report in here. Maybe there is such a support guide somewhere but I have not been able to find it and I just did another search just now to see if I could find one.

This is of course not too uncommon when going from an "open source" situation to one where you offer a commercial version as well, and I fully understand that there are a lot of challenges involved with this and I don't doubt that everyone at ABP (Volosoft) is working hard and doing what they can. At the same time, you are asking for our feedback so we should give it as it is.

is ABP commercial using Blazorise Free tier? it's showing a message to purchase commercial version

Has ABP responded to this yet and what version of Blazorise is actually included with ABP Commercial as of now?

ABP Commercial uses the Blazorise commercial version.

  • https://commercial.abp.io/faq#blazorise-license
  • https://commercial.abp.io/faq#blazorise-support

Just to clarify, would this be once license per developer you have assigned a ABP Commercial license to? From what I remember, ABP Commercial does not use "organizational email" like info@company.com but instead individual accounts connected to an organization/license like myname@company.com. Mainly asking as if you only get one account at Blazorise, you probably would want it to be info@company.com rather than somename@company.com.

Perhaps this should be moved to a separate ticket as it isn't really a 8.2 bug anymore it seems.

Please write only bugs related to 8.2.x under this topic. Otherwise, everyone who subscribed to this topic will see your personal comments and questions, which will be time-consuming for them. Contact info@abp.io for the licensing questions.

OP actually says "Feel free to report any bugs, issues, and problems." but sure.

I find that it hard to know if reported bugs, issues and problem in this thread is actually looked upon by the ABP Team and also to be able to track progress with them. So far it seems to be mostly us customers being active in here and with limited feedback from the ABP Team. I believe that with more feedback, more users of the RC versions would probably feel that it was worth reporting about problems which would be beneficial to us all. Thanks.

Showing 51 to 60 of 171 entries
Made with ❤️ on ABP v9.0.0-preview Updated on September 20, 2024, 08:30