Skip to content

Build and Test

Bogdan Gavril edited this page Jan 23, 2019 · 24 revisions

Visual Studio 2017 installation

Make sure you install VS with the following workloads:

  • .Net Desktop Development
  • Universal Windows Platform Development
  • Mobile Development with .Net
  • .Net Core cross-platform development

Some of the sample apps will require extra components, such as Windows SDKs, .Net Framework SDKs etc. You can either ignore those projects (unload them) or follow the instructions / error messages to install the extra components.

Visual Studio for Mac

MSAL is a multi-target library and at the time of writing, VS for Mac is not able to understand and layout this project correctly. You can still build from the command line.

Build

  1. (Windows only) Disable strong name validation on your dev box - Admin Developer Command Prompt, type "sn -Vr *"
  2. 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.
  3. Build in VS or via the command line with "msbuild /t:restore" and "msbuild"

Run tests

You won't be able to run the Integration test or Automation tests because they require access to a Microsoft KeyVault which is locked down. These tests will run as part of our DevOps pipelines though.

Run the unit tests from the assemblies:

  • Microsoft.Identity.Test.Unit.net45
  • Microsoft.Identity.Test.Unit.netcore

Getting started with MSAL.NET

Acquiring tokens

Web Apps / Web APIs / daemon apps

Desktop/Mobile apps

Advanced topics

FAQ

Other resources

Clone this wiki locally