Consider use of branches for different NET-runtime versions #29

Open
opened 2026-01-29 22:03:41 +00:00 by claunia · 0 comments
Owner

Originally created by @norvegec on GitHub (Mar 16, 2015).

My goal is to have NET3.5-targeted project with tests.
Afaik, Microsoft unit test projects require NET3.5 or newer. SharpCompress.NET2 is easily upgradeable to 3.5 (just remove LinqBridge and target 3.5).
The problems with different runtime versions had arosed, when I cloned the SharpCompress.Test to target NET3.5. Some of those problems are, for example: optional parameters, absence of some IO.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) and Windows 2008 R2 SP1 (server) are shipped with NET 3.5.

Originally created by @norvegec on GitHub (Mar 16, 2015). My goal is to have `NET3.5`-targeted project with tests. Afaik, Microsoft unit test projects require `NET3.5` or newer. `SharpCompress.NET2` is easily upgradeable to 3.5 (just remove `LinqBridge` and target 3.5). The problems with different runtime versions had arosed, when I cloned the `SharpCompress.Test` to target `NET3.5`. Some of those problems are, for example: optional parameters, absence of some `IO.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) and `Windows 2008 R2 SP1` (server) are shipped with `NET 3.5`](http://en.wikipedia.org/wiki/.NET_Framework#Versions).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/sharpcompress#29