Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split DotKEGG into Domain and Operations Assemblies #25

Open
Rabadash8820 opened this issue Apr 7, 2017 · 0 comments
Open

Split DotKEGG into Domain and Operations Assemblies #25

Rabadash8820 opened this issue Apr 7, 2017 · 0 comments
Assignees
Projects

Comments

@Rabadash8820
Copy link
Owner

Rabadash8820 commented Apr 7, 2017

DotKEGG needs to target .NET 3.5 so it can be used in Cell. However, most people using DotKEGG will probably be using .NET 4 or later, with access to the TPL and async/await programming, and will want those more modern features. Therefore, we should split DotKEGG into two assemblies:

  1. DotKEGG.Domain: contains the types that are basically just POCOs, including KeggId and its subclasses, KeggDb and its subclasses, and all the future database entry classes. This assembly should target .NET Framework 3.5.
  2. DotKEGG.Operations: contains the KEGG operation classes, including KeggInfo, KeggList, KeggGet, KeggLink, etc. There will be two versions of this assembly, one targeting .NET Framework 3.5, and one targeting .NET Framework 4 and later. Only the latter will support async methods.

Of course, both assemblies should be provided in the NuGet package. NuGet handles adding references to the proper assembly versions.

@Rabadash8820 Rabadash8820 added this to Backlog in DotKEGG Apr 7, 2017
@Rabadash8820 Rabadash8820 moved this from Backlog to Dev Ready in DotKEGG Apr 7, 2017
@Rabadash8820 Rabadash8820 self-assigned this Apr 7, 2017
@Rabadash8820 Rabadash8820 moved this from Dev Ready to Backlog in DotKEGG Apr 13, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
DotKEGG
Backlog
Development

No branches or pull requests

1 participant