Closed sturlath closed 1 year ago
Blazorise 1.1.4 will be available in ABP 7.0: https://github.com/abpframework/abp/issues/14833
Yes, I know that but I was wondering why it wasn´t working updating to minor version of Blazorise out-of-band with abp.io versions like it has been possible before?
I understand major version that there might be some incompatibility but why don´t you make sure that we can take advantage of versions that e.g., fix memory issues etc. Let's say my subscription of abp would have ended with 6.0.1 I wouldn't have been able to fix major things like that without buying another license (good for you bad for me). Luckily that's not my issue atm.
So, why does apb.io need to brake and is it possible going forward to have this in mind?
Yes, usually compatible.
ABP 6.0 and Blazorise 1.0 are based on NET 6.0. but start from Blazorise 1.1, it's based on NET7.0. this is a huge change : ). if there are some bugs we release a minor version to fix them, same for Blazorise.
Is there an existing issue for this?
Description
When trying to update a 6.0.1 version (community and commercial) with Blazorise 1.1.4.1 (and every version down to 1.0.6) throw the following exception when run
There is no abp.io error in there so I have reported this to Blazorse here.
I have usually been able to update Blazorise out of band with the abp.io versions and would really like to be able to do that.
So is the problem your side or Blazorise?
Reproduction Steps
Update a 6.0.1 version to newest Blazorise version and see it fail.
Expected behavior
Be able to update Blazorise out-of-band to abp.io versions
Actual behavior
Error
Regression?
Yes, I was able to update before!
Known Workarounds
No response
Version
6.0.1
User Interface
Blazor
Database Provider
EF Core (Default)
Tiered or separate authentication server
Separate Auth Server
Operation System
Windows (Default)
Other information
No response