microsoft / microsoft/sqlmanagementobjects
Nuget packages after 172.52.0 do not support netstandard2.0
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 143
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
I tried using the most recent version (172.64.0 at time of writing) in a netstandard2.0 project, and it failed to restore. I suspect that's because 172.64.0 doesn't explicitly support netstandard2.0.
Version 172.52.0 is the newest version that works. Was removing support in later versions deliberate? If it was, what is the intended way forward for people using SMO in netstandard projects? If it wasn't deliberate, is there any chance of getting a new version out that does support it (even if it's just versioned as 172.64.1 or 172.64.0-netstandard or something, with no changes from the current 172.64.0)?
I don't think there's any particular bits in 172.64 that I need right now, so using 172.52 isn't a showstopper, but I do like to keep my references up-to-date as far as I can.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the NuGet metadata and target frameworks for versions 172.52.0 and 172.64.0, then reproduce restore in a netstandard2.0 project. Done means confirming whether support was intentionally removed and either restoring netstandard2.0 compatibility in a subsequent package or documenting the intended path for affected users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100