Building logic on top of the target framework version is super helpful, but it would be easier if _TargetFrameworkVersionWithoutV was public. current logic only duplicates it. It is super small (.TrimStart('vV')
) and should be exposed publicly.
Mabe we can find a better name but that's irrelevant. Having something to compare against is helpful in custom build targets.
Is this reasonable to do?
We've been talking (https://github.com/Microsoft/msbuild/issues/3212#issuecomment-413956874) about introducing a new MSBuild version-comparison function that would ignore leading [vV]
. Would that be enough for your needs?
Hellz yes.
More comparison functions are great but having something that is easy to understand and use would also be great..
Most helpful comment
We've been talking (https://github.com/Microsoft/msbuild/issues/3212#issuecomment-413956874) about introducing a new MSBuild version-comparison function that would ignore leading
[vV]
. Would that be enough for your needs?