Azure-docs: Code error

[Rachitgupta1994]

Hi. I am trying to implement azure ad login in Xamarin app. The code line gives error

new PlatformParameters(this)

PlatformParameters does not contain a constructor that takes 1 argument.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e36707dc-b98b-cc04-8445-4ccd26169952
• Version Independent ID: 6c8c507a-5b4d-d93c-c89d-481c6852c420
• Content: Azure AD Xamarin getting started
• Content Source: articles/active-directory/develop/active-directory-devquickstarts-xamarin.md
• Service: active-directory
• GitHub Login: @jmprieur
• Microsoft Alias: jmprieur

[MohitGargMSFT]

@Rachitgupta1994 Thanks for your feedback! We will investigate and update as appropriate.

[MohitGargMSFT]

@Rachitgupta1994 I have assigned the issue to the author to investigate and update as appropriate.

[CelesteDG]

@Rachitgupta1994 just a quick update that @jmprieur is currently on vacation, but I'll follow up with him once he gets back.

[andretms]

@Rachitgupta1994 - thanks for reporting the issue. The problem is that ADAL version referenced in the sample - 3.9.304210845 - does not accept this signature. Current versions do (see here) accept this parameter.

To solve your problem, please go ahead and update Microsoft.IdentityModel.Clients.ActiveDirectory packages to the newest version.

However, the sample linked to this doc is being archived and no longer maintained. I recommend active-directory-dotnet-native-multitarget sample instead. We will retire this document and point to the new sample in the next few days. Again, thank you to report the issue.

[mtillman]

@Rachitgupta1994 - Did this resolve your issue? If not, feel free to re-open this issue.

please-close

[femsulu]

@Rachitgupta1994
We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

[sundhar19]

Is there any solution for this. I am also getting the same issue. I am using the Microsoft.IdentityModel.Clients.ActiveDirectory version 3.19.6 which is highest version as of now

[CelesteDG]

Hi @sundhar19 - Were you using the sample linked from the doc or the one recommended here: active-directory-dotnet-native-multitarget sample instead. We will retire this document and point to the new sample in the next few days. Again, thank you to report the issue.

[jmprieur]

@sundhar19
With a recent version of Xamarin, we have noticed that the NuGet package manager did not resolve correctly the right ADAL.NET platform; if you look in your project, you'll see that the HintPath for the ADAL.NET DLL is under package\Microsoft.IdentityModel.Clients.ActiveDirectory\netstandard1.3 whereas it should be resolved with package\Microsoft.IdentityModel.Clients.ActiveDirectory\xamarin.Android.10

Is it what you are experiencing?
cc: @CelesteDG

[jennyf19]

@sundhar19 @Rachitgupta1994 Did @jmprieur's solution above solve the issue for you?

[judemars]

I am also experiencing the same issue and updating to the latest version of Microsoft.IdentityModel.Clients.ActiveDirectory, 3.19.6, did not solve the problem. Interestingly, this same version does work in the AAD sample project I cloned from here https://github.com/Microsoft/vsts-auth-samples/tree/master/ManagedClientConsoleAppSample, which targets .net framework whereas my app targets .net core. When I follow the reference for the new PlatformParameters in my app I see a definition for platformparameters which has only one constructor with no args, whereas the one in the sample app has more options. See the attached picture, where the instance above is the sample app targetting .net framework and the instance below is targetting .net core, but both have exact same version of nuget package.

[linuxcat]

Yup, .NetCore does not support it is there a workaround?

[jennyf19]

@judemars @linuxcat

Thanks for the information. You are seeing differences between .NetCore and .Net Framework PlatformParameters implementations because .NetCore does not provide UI, so there is no possibility for user interaction. See our wiki for more information. The PlatformParameters are for the user interaction during acquire token interactive flows on the various platforms supported by Adal.

[ehsan67]

This issue still exists in 4.3.0.

[RobinHSanner]

This issue needs to be reopened. It still exists in a .NET Core app as of 4.5.1 of the nuget package. Without being able to specify this parameter (regardless of whether it actually accomplishes anything) you can't specify the AcquireTokenAsync overload that takes resourceuri, applicationid, redirecturi. Supplying new PlatformParameters() results in an exception NotImplementedException. At the very minimum add the property for PromptBehavior and hard code it to PromptBehavior.Never.

[shankarab]

This issue still persists. I'm writing a desktop app in .NET Core 3.1, and I need this constructor to force the user to login. Possible to get this fixed?

[jmprieur]

We recommend that you don't use ADAL.NET but MSAL.NET.
See https://aka.ms/aaddevsamplesv2

[2552Software]

ADAL.NET used all over the place by Microsoft. ADAL.NET is still supported by Microsoft. I get that you want us to move forward but even Microsoft is not moving...

[jmprieur]

@2552Software : actually Microsoft is moving. you'll see more and more documentations mentionning ADAL.NET being changed to using MSAL.NET.
cc: @aiwangmicrosoft
also this quickstart does not exist any longer

[2552Software]

Thank you for the note and yes, I am seeing the samples go away and I do understand why at least at some level.

What is confusing to me is how to do a resource login in MSAL.NET such as ADAL.NET's authenticationContext.AcquireTokenAsync(Resource, ClientId, new Uri(LocalRedirectUri), new PlatformParameters(PromptBehavior.Auto)); I do not think this is possible.

I am also a bit confused because the open source Azure command line and the Azure SDK all use ADAL.NET, its pretty deeply ingrained and that was what I am referring to.

But they do not enable the call above and as far as I know this sample call above cannot work on a web server with ADAL.NET so my current code is stuck with ADAL.NET and I cannot move it to a web server.

I hope this observation, and its more a question, make sense and I should have started here vs my initial note. Anyway, thanks for any input and my preference is to always use the latest from Microsoft. I am just stuck on this one.