Closed norvegec closed 8 years ago
Branches could work. First, I'd want to reduce the supported frameworks.
Ideally, I was going to drop support for anything not portable or pre-4.0. (or maybe pre-4.5 because of async/await, not that it is used). I just literally have not had the time to work on this for years now.
Why support 3.5?
Why support 3.5?
I am planning to use it as part of SharePoint 2010
solution.
I'm going to use xproj for this when NET Core and ASP.NET get released
My goal is to have
NET3.5
-targeted project with tests. Afaik, Microsoft unit test projects requireNET3.5
or newer.SharpCompress.NET2
is easily upgradeable to 3.5 (just removeLinqBridge
and target 3.5). The problems with different runtime versions had arosed, when I cloned theSharpCompress.Test
to targetNET3.5
. Some of those problems are, for example: optional parameters, absence of someIO.Directory
methods,IEnumerable<T>
is not covariant.So, can we replace preprocessor-directives style of code with project-by-framework style? We can use different branches to simplify support. What do you think?
As a side note, do we really need to support NET2 version?
Windows 7
and newer (client) andWindows 2008 R2 SP1
(server) are shipped withNET 3.5
.