Added explicit support for .NET 4.6.1 and .NET Core 2.0.#400
Added explicit support for .NET 4.6.1 and .NET Core 2.0.#400ericnewton76 merged 1 commit intocommandlineparser:developfrom GriffinPlus:master
Conversation
Eliminates the need for interfacing libraries reducing the footprint of an application built with the CommandLine library.
|
Sorry for the force-push, my business e-mail address evaded ;-) |
|
Force pushes are okay. Thanks for the contribution. I was actually working towards making this change myself... you beat me to it... ;-) |
|
Thank you :-) |
|
@ravenpride Have a look to a discussion in sept,2018 posted by me to the Nuget team related to the same problem , with the title:
and also this discussion. The nuget team suggestion was:
I suggested to modify nuspec file by adding empty dependency group to avoid installing many packages of netstandard15 for net46x projects So, It's enough to support net45 with netstandard2 to avoid these huge dll(s). |
I've added support for building the library explicitly for .NET 4.6.1 and .NET Core 2.0. Although .NET Standard 2.0 is implemented by these frameworks, referencing a .NET Standard library seems to pull in a lot of interfacing libraries that simply map calls from .NET Standard to the effective target platform.
This is the output directory of a simple .NET 4.6.1 console application just executing
new CommandLine.Parser();And this is the output directory of the console application after adding explicit support for.NET 4.6.1:
The change needed is really small as Visual Studio 2017 supports building for multiple target frameworks out of the box. Furthermore all libraries are automatically packed into the NuGet package.
Greetings :-)