-
Notifications
You must be signed in to change notification settings - Fork 353
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
[Feature Request] netstandard 2.0 or 2.1 support #1991
Comments
7 tasks
@bgavrilMS : would that issue be related as well to the suppression of the reference libraries? |
Not so much... |
7 tasks
Repository owner
moved this from Waiting for Code Review
to Fixed
in MSAL Customer Trust / QM
Jul 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Customers are asking for a more capable .net standard version of MSAL, which allows for interactive flow. Some scenarios are:
MSAL usage in plugin scenarios - e.g. if I want to write a roslyn analyzer, it will be consumed by .net classic or by .net core but this is not known until my analyzer is deployed into VS or run via command line. In this case, we can only rely on MSAL .netstandard
Similar to the above scenario, PowerShell also has pretty complex logic to switch between .net classic and .net core.
With Unity, only the netstandard version can be consumed (by unzipping the nuget package and selecting the DLL). We can improve the experience by offering a more capable netstandard
For Blazor applications
Describe the solution you'd like
.net standard version of MSAL.
The text was updated successfully, but these errors were encountered: