Should there be a .NET 5.0 target now?

[gitfool]

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:

• WireMock.Net
• WireMock.Net.StandAlone

Specify:

<TargetFrameworks>net451;net452;net46;net461;netstandard1.3;netstandard2.0;netstandard2.1;netcoreapp3.1</TargetFrameworks>

Also, some of those are now well out of support and so could possibly be dropped?

[StefH]

#543

[StefH]

Hello @gitfool,

• Can you explain this: WireMock.Net seem to work fine, apart from logging ?
• Some frameworks are indeed out of support, however for now I keep these. Probably next year I will remove some.

[gitfool]

@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.0 target framework is advisable.

[StefH]

OK.
PR is merged