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 like this project, but its dependency on .net framework is a hindrance to those of us that have migrated on to .net core. We'd like to use it as a nuget package, but we're unable to use it as-is. This project is certainly able to utilize .net standard rather than .net 3.5, but I understand why you wouldn't upgrade if you have internal projects that are still running on framework 3.5 - there is no .net standard compatibility for that version of the framework. Is that the case? Thanks!
The text was updated successfully, but these errors were encountered:
We like this project, but its dependency on .net framework is a hindrance to those of us that have migrated on to .net core. We'd like to use it as a nuget package, but we're unable to use it as-is. This project is certainly able to utilize .net standard rather than .net 3.5, but I understand why you wouldn't upgrade if you have internal projects that are still running on framework 3.5 - there is no .net standard compatibility for that version of the framework. Is that the case? Thanks!
The text was updated successfully, but these errors were encountered: