-
Notifications
You must be signed in to change notification settings - Fork 217
Build and Test
-
Navigate to the main page for the Microsoft Identity Web repo.
-
From the GitHub UI, click clone or download.
-
Alternatively open a dev command line and run:
git clone https://github.com/AzureAD/microsoft-identity-web.git
The project is cloned into a local folder.
-
Open Microsoft.Identity.Web.sln and build it in Visual Studio 2022. Note the Troubleshooting building in Visual Studio section below.
-
Alternatively, open a dev command line and build with
dotnet msbuild Microsoft.Identity.Web.sln
or just,
dotnet msbuild
You won't be able to run the Integration tests because they require access to a Microsoft Key Vault which is locked down. These tests run daily as part of our Azure DevOps pipelines.
To run the unit tests from the assembly Microsoft.Identity.Web.Test. For this:
cd tests\Microsoft.Identity.Web.Test
dotnet test
From Visual Studio or from the command line. If you wish to control the versioning, use the p:ClientSemVer
property
dotnet pack -p:ClientSemVer=1.0.0
If you executed the command above, you'll find the NuGet packages generated under:
- src\Microsoft.Identity.Web\bin\Debug\Microsoft.Identity.Web.1.0.0.nupkg
- src\Microsoft.Identity.Web.UI\bin\Debug\Microsoft.Identity.Web.UI.1.0.0.nupkg
- ProjectTemplates\bin\Debug\Microsoft.Identity.Web.ProjectTemplates.0.x.y.nupkg
The symbols are also generated:
- src\Microsoft.Identity.Web\bin\Debug\Microsoft.Identity.Web.1.0.0.snupkg
- src\Microsoft.Identity.Web.UI\bin\Debug\Microsoft.Identity.Web.UI.1.0.0.snupkg
For the moment, Microsoft.Identity.Web leverages a preview version of .NET 8.0. To build in Visual Studio, you will need to enable Visual Studio to use preview SDKs. For this go to Tools | Options | Environment| Preview features | Use previews of the .NET Core SDK (requires restart), and restart Visual Studio.
- Home
- Why use Microsoft Identity Web?
- Web apps
- Web APIs
- Using certificates
- Minimal support for .NET FW Classic
- Logging
- Azure AD B2C limitations
- Samples
- Web apps
- Web app samples
- Web app template
- Call an API from a web app
- Managing incremental consent and conditional access
- Web app troubleshooting
- Deploy to App Services Linux containers or with proxies
- SameSite cookies
- Hybrid SPA
- Web APIs
- Web API samples
- Web API template
- Call an API from a web API
- Token Decryption
- Web API troubleshooting
- web API protected by ACLs instead of app roles
- gRPC apps
- Azure Functions
- Long running processes in web APIs
- Authorization policies
- Generic API
- Customization
- Logging
- Calling graph with specific scopes/tenant
- Multiple Authentication Schemes
- Utility classes
- Setting FIC+MSI
- Mixing web app and web API
- Deploying to Azure App Services
- Azure AD B2C issuer claim support
- Performance
- specify Microsoft Graph scopes and app-permissions
- Integrate with Azure App Services authentication
- Ajax calls and incremental consent and conditional access
- Back channel proxys
- Client capabilities