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
I have one project that I am working on that is in part based on .NET Framework 4.7.2. It is currently using CqrsLite 1.33.0. Everything is working fine. However, when I attempt to upgrade CqrsLite to version 1.34.0 i get:
Could not install package 'CqrsLite 1.34.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.7.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Was dropping support for .NET Framework 4.7.2 intentional or accidental?
The text was updated successfully, but these errors were encountered:
Hi. Sorry for the slow reply. It was intentional as I wanted to make the code base a bit simpler and skip all compiler flags to support too many runtimes. Is there a reason you can't upgrade to .NET 5? I'm open to supporting 4.7 again if there's a demand.
Thanks for your reply. My project is based in part on an old version of Microsoft Dynamics GP. Microsoft has a newer Cloud version that my customer's don't want to use. So I am stuck with .net Framework. I do hope you consider supporting 4.7 again.
I have one project that I am working on that is in part based on .NET Framework 4.7.2. It is currently using CqrsLite 1.33.0. Everything is working fine. However, when I attempt to upgrade CqrsLite to version 1.34.0 i get:
Could not install package 'CqrsLite 1.34.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.7.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
Was dropping support for .NET Framework 4.7.2 intentional or accidental?
The text was updated successfully, but these errors were encountered: