There's a high coupling between packages in Liquid. While OnAzure, OnAWS and OnGoogle only provide implementations for high level abstractions, those implementations are on packages are have transitional dependencies to Liquid.Base that depends on ASP.NET.
Fixing this isn't exactly easy because we need to rethink the whole package structure, but it's actually more feasible than it looks. Also, if we are able to maintain most namespaces, impact for users is minimal - all it means is that he'll be downloading more/different nugets.
There's a high coupling between packages in Liquid. While OnAzure, OnAWS and OnGoogle only provide implementations for high level abstractions, those implementations are on packages are have transitional dependencies to Liquid.Base that depends on ASP.NET.
Fixing this isn't exactly easy because we need to rethink the whole package structure, but it's actually more feasible than it looks. Also, if we are able to maintain most namespaces, impact for users is minimal - all it means is that he'll be downloading more/different nugets.