mirror of
https://github.com/wiremock/WireMock.Net.git
synced 2026-01-11 21:10:32 +01:00
Should there be a .NET 5.0 target now? #316
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gitfool on GitHub (Nov 25, 2020).
After porting projects to .NET 5.0, unit and integration tests using WireMock.Net seem to work fine, apart from logging "WireMock.Net server using .NET Core 3.1". Not sure when it's needed but I noticed there are a lot of target frameworks for some reason:
Specify:
Also, some of those are now well out of support and so could possibly be dropped?
@StefH commented on GitHub (Nov 26, 2020):
https://github.com/WireMock-Net/WireMock.Net/pull/543
@StefH commented on GitHub (Nov 26, 2020):
Hello @gitfool,
WireMock.Net seem to work fine, apart from logging?@gitfool commented on GitHub (Nov 26, 2020):
@StefH the logging comes from the hard wired log message determined by target framework at compile time (AspNetCoreSelfHost .RunHost), which you address in PR 543 along with a few other tweaks that make me think a new release with
net5.0target framework is advisable.@StefH commented on GitHub (Nov 28, 2020):
OK.
PR is merged