Skip to content

Consolidating supported TargetFrameworks to netstandard2.0 #1

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

Closed
3 tasks
Arlodotexe opened this issue Jun 23, 2022 · 1 comment · Fixed by #2
Closed
3 tasks

Consolidating supported TargetFrameworks to netstandard2.0 #1

Arlodotexe opened this issue Jun 23, 2022 · 1 comment · Fixed by #2

Comments

@Arlodotexe
Copy link
Collaborator

Background

We're forking and maintaining the amazing work done by Richard Schneider, who appears to have permanently logged off since November 2019.

To support IPFS in the .NET ecosystem, I'll be maintaining this repo and the net-ipfs-http-client repo, approving PRs, and generally helping the community pick up where Richard left off.

First steps

Before we can have PRs rolling in, one of the first things we need to do is consolidating our TargetFramework to netstandard2.0.

There's a few reasons for this:

Checklist

  • All TargetFrameworks have been removed, except for netstandard2.0
  • All compilation conditionals (#if NET45, etc) have been removed.
  • Tests have been consolidated to a single .NET 6 project, referencing a single NS2.0 project
@Arlodotexe
Copy link
Collaborator Author

Linking ipfs-shipyard/net-ipfs-http-client#1

stevefan1999-personal referenced this issue in stevefan1999-personal/net-ipfs-core Mar 12, 2023
…t.Sdk-17.0.0

chore(deps): bump Microsoft.NET.Test.Sdk from 16.2.0 to 17.0.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant