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
Personally, I think it's time to leave the .NET Framework behind.
This project doesn't use anything like WinForms or WPF, so there are no issues there.
However, some of the sample projects are .NET Framework, as is the WebApi package. Which is why #32 failed rather spectacularly and I had to reset the whole thing (I had the Windows Specific Projects hidden and forgot - whoops...).
Update readme to indicate that the current version is the last which will support .NET Framework and do a major version number bump.
Delete Hypermedia.Sample.WebApi
Delete Hypermedia.WebApi
Delete Hypermedia.JsonApi.WebApi
Upgrade all .NET Standard 1.4 Libs to .NET 6
Hypermedia.AspnetCore will probably need a rewrite the API has changed so much
Refactor these projects to be more canonically .NET 6-like... Things like adding file-scoped namespeaces.
Look into replacing Newtonsoft with System.Text.Json everywhere but I'd recommend waiting for Create Test Suite #42 to be completed first or there will be a nightmare regression testing it.
The text was updated successfully, but these errors were encountered:
@hugesjs, how about client-side code that can only target netstandard2.0, for example? I am asking because I am looking for a client-side library that I ultimately use in a project that is -- very unfortunately -- tied to .NET Framework. Without going into further details, this is Microsoft's choice, not mine. I would love to be on .NET 6 etc. with all our code base.
If there is no support for netstandard2.0 at least, I would have to look elsewhere.
Personally, I think it's time to leave the .NET Framework behind.
This project doesn't use anything like WinForms or WPF, so there are no issues there.
However, some of the sample projects are .NET Framework, as is the WebApi package. Which is why #32 failed rather spectacularly and I had to reset the whole thing (I had the Windows Specific Projects hidden and forgot - whoops...).
The benefits of the upgrade to .NET 6 include:
System.Text.Json
My suggested course of action would be:
Hypermedia.Sample.WebApi
Hypermedia.WebApi
Hypermedia.JsonApi.WebApi
System.Text.Json
everywhere but I'd recommend waiting for Create Test Suite #42 to be completed first or there will be a nightmare regression testing it.The text was updated successfully, but these errors were encountered: