Something I have found particularly frustrating is that unless you're on an enterprice license, you can't even reach out to the team directly for feedback or update - it''s a "post and wait" situation. We can't tag anyone, there is no escallation for priority issues, and no way to get updates.
Normally, this wouldn't bother me too much. Minor issues are usually something you can work elsewhere while you wait on, but something of this scale? It's crazy.
Thanks for your effort summarizing the situation and grouping all incidents :D
That said, it would be about time for Volo to shows up, even if the incident is not resolved yet, any kind of communication would be quite appreciated.
Thanks for the update. i couldn't find any other mention to this specific problem...
At least i can stop rebooting, restarting VS, deleting bin/obj, delete nuget cache etc!
Thank you
Ok thanks, ill add it.
Just to be sure i understand correctly, if the issue we do submit is marked as an actual bug and not a wrong config / usage, we get our 'credit' back, right?
Perfect!
As for the .netstandard, we moved the whole solution to .net6.
Thanks
Thanks you! closing it ;)
Do you know then how we can change the picture on the login screen?
Thank you
Thanks, so far the favicon and logo is working.
On my BrandingProvider tough, i only have those properties 
and the logo url actually is working (so it seems we dont have to override the css ;)).
Please note that i am using the not tiered version
Thank you
Thank you, it does work.
Also, there aint no doc either for those 2 other customization that probably everyone needs:
Thank you
Hi @maliming,
Ive deployed the app on an azure app service and the performance are good (production release).
Might have been a problem with my local computer.
Thank you
