Stefan, I think you'd indeed want to target the lowest netstandard version possible without having to sacrifice features. We could always have both 1.3 and 1.6 versions, but I don't even know if 1.6 contains those missing ADO.NET features (does anyone ? :p). I get the impression that each day brings a new netstandard version (1.7 and 2.0 are already in the works, if I'm not mistaken).
For SSH.NET, I decided to stop using "target framework" compilation symbols (like NET_45) and instead opted for API feature toggles (like FEATURE_SOCKET_POLL). Perhaps also something to consider for log4net. Regards, Gert PS. Sorry for the reply format (Outlook ...). -----Original Message----- From: Stefan Bodewig [mailto:bode...@apache.org] Sent: zondag 11 september 2016 12:25 To: 'Log4NET Dev' <log4net-dev@logging.apache.org> Subject: Re: netstandard version of the .NET Core build On 2016-09-11, Gert Driesen wrote: > I suppose it's 1.3 because 1.0 has an even more limited API surface. > A lot of CoreFX packages are not available for netstandard 1.0. > For SSH.NET - an OSS project I spend most of my time on right now - I > also chose 1.3 because of this. Thanks, this explains why I wouldn't want to use something lower than 1.3. But why not 1.6? People using .NET Framework 4.5 can and should use our net-4.5 assembly as it - unlike the netsandard1.3 version - contains the ADO.NET appender, for example. Stefan
