-
Notifications
You must be signed in to change notification settings - Fork 214
Pre requisites to build ADAL.NET and MSAL.NET
The following are instructions to setup Visual Studio to build the Combined.NoWinRT.sln
-
Install or update Visual Studio 2017 with the following workloads:
- Universal Windows Platform
- Mobile Development with .NET
- .NET Core cross-platform development
-
Then from the "Individual Components" tab, you'll need these additional items:
- .NET Framework 4.5 targeting pack
- .NET Framework 4.5.2 targeting pack
- .NET Framework 4.6.1 SDK
- .NET Framework 4.6.1 targeting pack
- .NET Framework 4.6.2 targeting pack
- Android SDK setup (API level 27)
-
Android SDK level 24 and 26 are also required. These are not installed through the VS Installer, so instead use the Android SDK Manager (Visual Studio > Tools > Android > Android SDK Manager…)
This should be enough to allow you to build the libraries from the adalv3/dev branch. For the dev branch, you also need to install Visual Studio 2015 (see below)
- If you get an exception similar to "System.InvalidOperationException: Could not determine Android SDK location" while restoring the NuGet packages, make sure you have the latest Android SDK installed (27 at the time of writing). If you do, you probably hit a bug with the VS installer - uninstall and reinstall the SDK from the Visual Studio Installer.
- If you get exceptions requiring you to install netcore4.5, this can only be fixed by installing Visual Studio 2015
- If you are getting exceptions such as The reference assemblies for framework ".NETCore,Version=v4.5.1" were not found then you are missing VS 2015 (see below)
If you still get exceptions building the solutions, there is a PS script you can run that will tell you which VS 2017 components you are missing - you can find at /build/dev_box.ps1 (currently in dev branch)
This is an additional requirement to build the dev branch.
Perform a custom install of Visual Studio 2015 Update 3 and include "Windows 8.1 and Windows Phone 8.0 / 8.1 Tools" and "Universal Windows Apps" components.
- Home
- Why use ADAL.NET?
- Register your app with AAD
- AuthenticationContext
- Acquiring Tokens
- Calling a protected API
- Acquiring a token interactively
- Acquiring tokens silently
- Using Device Code Flow
- Using Embedded Webview and System Browser in ADAL.NET and MSAL.NET
- With no user
- In the name of a user
- on behalf of (Service to service calls)
- by authorization code (Web Apps)
- Use async controller actions
- Exception types
- using Broker on iOS and Android
- Logging
- Token Cache serialization
- User management
- Using ADAL with a proxy
- Authentication context in multi-tenant scenarios
- Troubleshooting MFA in a WebApp or Web API
- Provide your own HttpClient
- iOS Keychain Access