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

Update Microsoft.Azure.KeyVault to support .NET Standard 2.0 #3333

natemcmaster opened this Issue Jun 7, 2017 · 5 comments


None yet
7 participants

natemcmaster commented Jun 7, 2017

Currently, there are some APIs in Microsoft.Azure.KeyVault only available when targeting .NET Framework, for instance Microsoft.Rest.Azure.Authentication.ClientAssertionCertificate. With the thousands of new APIs available in .NET Standard 2.0 (compared to netstanard1.5), this restriction may not be necessary anymore.

FYI - upstream, we've converted Microsoft.Extensions.Configuration.AzureKeyValue to .NET Standard 2.0. This is the only API missing from the .NET Standard build, which means we also have to cross-compile for .NET Framework.


This comment has been minimized.


shahabhijeet commented Jun 30, 2017

@natemcmaster we have another issue tracking this move.
We need to plan this and will keep you updated.

@shahabhijeet shahabhijeet added Team and removed KeyVault labels Jun 30, 2017


This comment has been minimized.

natemcmaster commented Feb 1, 2018

Ping. Any updates to your plans?


This comment has been minimized.

komaflash commented May 7, 2018

@RandalliLama or @shahabhijeet
Ping. Any updates to your plans?


This comment has been minimized.

garfbradaz commented Nov 6, 2018

Any news?


This comment has been minimized.


schaabs commented Nov 13, 2018

@natemcmaster @garfbradaz The version of .NET we reference is determined by shared project files in the azure-sdk-for-net repo. Hence we cannot move the Key Vault SDK packages to .NET Standard 2.0 until the repo moves as a whole. According to the comment from @shahabhijeet above this work is being tracked by issue #3438

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment