-
Notifications
You must be signed in to change notification settings - Fork 377
Build and Test
Prerequisites to build MSAL.NET can be found here
MSAL .Net supports many target frameworks, by default it does not enable the mobile targets and the legacy targets. Unit tests will run with these.
To load all targets, open this file and comment in the targets you are interested in.
To get MSAL to build for all the frameworks, you'll need a hefty Visual Studio 2019 installation plus several Windows SDKs.
Note: Do not use VS Code or VS for Mac as it is not able to understand and layout this project correctly.
Load LibsAndSamples.sln for a bigger solution with lots of apps that exercise MSAL. Load LibsNoSamples.sln for a small solution that has the library and the tests.
Note: if you run into strong name validation issues, please log a bug. Workaround is to disable it on your dev box by running Admin Dev Prompt > sn -Vr *
Microsoft contributors can run integration tests by following instructions here.
External contributors can only run the unit tests. The CI build will run integration tests.
To test an MSAL package, use the package command from VS. Or from the command line:
msbuild <msal>.csproj /t:pack /p:MsalClientSemVer=1.2.3-preview
- Home
- Why use MSAL.NET
- Is MSAL.NET right for me
- Scenarios
- Register your app with AAD
- Client applications
- Acquiring tokens
- MSAL samples
- Known Issues
- Acquiring a token for the app
- Acquiring a token on behalf of a user in Web APIs
- Acquiring a token by authorization code in Web Apps
- AcquireTokenInteractive
- WAM - the Windows broker
- .NET Core
- Maui Docs
- Custom Browser
- Applying an AAD B2C policy
- Integrated Windows Authentication for domain or AAD joined machines
- Username / Password
- Device Code Flow for devices without a Web browser
- ADFS support
- High Availability
- Regional
- Token cache serialization
- Logging
- Exceptions in MSAL
- Provide your own Httpclient and proxy
- Extensibility Points
- Clearing the cache
- Client Credentials Multi-Tenant guidance
- Performance perspectives
- Differences between ADAL.NET and MSAL.NET Apps
- PowerShell support
- Testing apps that use MSAL
- Experimental Features
- Proof of Possession (PoP) tokens
- Using in Azure functions
- Extract info from WWW-Authenticate headers
- SPA Authorization Code