You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have been using Westwind.Globalization for some time now on several of our sites. Previously we used the .NET Framework version and then upgraded to 3.1 Core and now attempting to upgrade to .NET 6/7. However, some of our developers have new Macs with the M chips and Windows 11 ARM and they are unable to run the latest version of Westwind.Globalization.AspnetCore since it references Westwind.Utilities.Data and uses System.Data.Sqlite (which doesn't support ARM) rather than Microsoft.Data.SqLite (which does support ARM via via SQLitePCLRaw.bundle_e_sqlite3).
Any suggestions on a workaround rather than forking and changing all the dependencies? Or maybe there is something I'm missing as it looks like the docs say to install Microsoft.Data.SqLite, but when I look at the SqlUtils it looks like it is still referencing System.Data.SqLite.
Thanks!
Chuck
The text was updated successfully, but these errors were encountered:
We have been using Westwind.Globalization for some time now on several of our sites. Previously we used the .NET Framework version and then upgraded to 3.1 Core and now attempting to upgrade to .NET 6/7. However, some of our developers have new Macs with the M chips and Windows 11 ARM and they are unable to run the latest version of Westwind.Globalization.AspnetCore since it references Westwind.Utilities.Data and uses System.Data.Sqlite (which doesn't support ARM) rather than Microsoft.Data.SqLite (which does support ARM via via SQLitePCLRaw.bundle_e_sqlite3).
Any suggestions on a workaround rather than forking and changing all the dependencies? Or maybe there is something I'm missing as it looks like the docs say to install Microsoft.Data.SqLite, but when I look at the SqlUtils it looks like it is still referencing System.Data.SqLite.
Thanks!
Chuck
The text was updated successfully, but these errors were encountered: