Targeting netstandard2.0/netstandard2.1

[carl-berg]

trafficstars

Current behavior when installing WebAnchor on a .net core 3.1 project is that it wants a lot of dependencies Since Webanchor supports netstandard2.0 (maybe could support netstandard2.1 aswell now?) i assume the culprit here is WebAnchor.Analyzers which targets only netstandard1.3

[carl-berg]

...could also be Castle.Core which only goes up to .NETStandard 1.5 which could be a harder nut to crack https://github.com/castleproject/Core/issues/407... but it does seem like they're working on it https://github.com/castleproject/Core/pull/485

[mattiasnordqvist]

I don't understand this. I've heard I should always target the lowest possible netstandard.

[carl-berg]

However, targeting lower .NET Standard versions introduces a number of support dependencies. If your project targets .NET Standard 1.x, we recommend that you also target .NET Standard 2.0. This simplifies the dependency graph for users of your library that run on .NET Standard 2.0 compatible frameworks, and it reduces the number of packages they need to download.

https://docs.microsoft.com/en-us/dotnet/standard/net-standard

[mattiasnordqvist]

Ok so target low and multitarget

[carl-berg]

Yeah, that's what i think is the recommended way

[mattiasnordqvist]

So I released 6.6.2 which also targets netstandard2.1. For some reason, I could not make the analyzer multitarget, and the vsix, which is netframework (has to be?) could not reference a package targeting netstandard2.1, so.... webanchor 6.6.2 still references the same analyzer. Hoping a bit that because it's a dev dependency it's going to work out fine anyways. We'll see

[mattiasnordqvist]

my dependency list still looked crazy I think. same for you @carl-berg ? Maybe the analyzer should be it's own package entirely, and not be referenced by webanchor at all.