Hi,
Thanks for the update - its very helpful.
Can you let me know if upcoming 13.2 has any bug fixes solely for .NET 8? In other words is it okay to stick with 13.1 for our .NET 8 upgrade - or is there some bug/issue we should be aware of that should push us to use 13.2? Its just that 13.2 will be so new.
Kieran
The 'high' breaking change put forward by MS in the link below - around Linq queries and contains in EF 8 - looks to be causing us issues on our own code when we upgrade our app from .NET 6 to .NET 8.
Has this change been tested/refactored for in AspNetZero 13.1.0 - or is it part of upcoming 13.2.0?
Also can we upgrade to 13.1.0 without upgrading our app from .NET 6 to .NET 8?
What is the expected release date of 13.2.0?
https://learn.microsoft.com/en-us/ef/core/what-is-new/ef-core-8.0/breaking-changes#sqlserver-contains-compatibility
Thanks
Version: 10.2.0
Hi there We were recently Pen Tested. They failed us on this:
"When an unauthenticated user browses to https://xxxx.xxx.net/, a request is automatically triggered to https://xxxx.xxx.net/AbpUserConfiguration/GetAll and contains information about the application"
Is there a way for us to hide/block access to this endpoint AbpUserConfiguration/GetAll as it contains alot of data useful in the wrong hands.
Thank you
Version: 10.2.0
Yes, we updated all the packages and to we are now on .5 We had references to moment in lost of places but that is now replaced with Luxon breaking any date controls we had.
What is the correct way to perform an upgrade, we are finding it very cumbersome.
Thank you.
What is your product version? 2.7.6
Hi there We have upgraded to the latest version and libraries of aspnetzero. In doing so, we have noticed that dateformats now use luxon.js
This has broken all of our date labels, datepickers.
What do you advise we do?