workos / workos-dotnet

Official .NET SDK for interacting with the WorkOS API

WorkOS .NET Library

The WorkOS library for .NET provides convenient access to the WorkOS API from applications using .NET. Supports .NET Standard 2.0+ and .NET Framework 4.6.1+

Documentation

See the API Reference for .NET usage examples.

Installation

There are several options to install the WorkOS .NET SDK.

Via the NuGet Package Manager

nuget install WorkOS.net

Via the .NET Core Command Line Tools

dotnet add package WorkOS.net

Via Visual Studio IDE

Install-Package WorkOS.net

Configuration

To use the WorkOS client, you must provide an API key from the WorkOS dashboard.

WorkOS.SetApiKey("sk_key123");

You can also optionally provide a custom HttpClient.

var client = new WorkOSClient(
    new WorkOSOptions
    {
        ApiKey = "sk_key123",
        HttpClient = ...,
    });
WorkOS.WorkOSClient = client;

Development and Testing

Run all tests with the following command:

dotnet test test/WorkOSTests/WorkOSTests.csproj

Run tests for a specific framework with the following command:

dotnet test test/WorkOSTests/WorkOSTests.csproj -f netcoreapp3.1

SDK Versioning

For our SDKs WorkOS follows a Semantic Versioning process where all releases will have a version X.Y.Z (like 1.0.0) pattern wherein Z would be a bug fix (I.e. 1.0.1), Y would be a minor release (1.1.0) and X would be a major release (2.0.0). We permit any breaking changes to only be released in major versions and strongly recommend reading changelogs before making any major version upgrades.

Beta Releases

WorkOS has features in Beta that can be accessed via Beta releases. We would love for you to try these and share feedback with us before these features reach general availability (GA). To install a Beta version, please follow the installation steps above using the Beta release version.

Note: there can be breaking changes between Beta versions. Therefore, we recommend pinning the package version to a specific version. This way you can install the same version each time without breaking changes unless you are intentionally looking for the latest Beta version.

We highly recommend keeping an eye on when the Beta feature you are interested in goes from Beta to stable so that you can move to using the stable version.

More Information

• Single Sign-On Guide
• Directory Sync Guide
• Admin Portal Guide
• Magic Link Guide

workos-dotnet's Issues

Method naming guidelines

What coding conventions is being followed for naming? Notice that the async methods are not suffixed with Async.

cite:
https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/concepts/async/task-asynchronous-programming-model#BKMK_NamingConvention

When will 1.9.0 nuget package be released?

1.8.0 is the only one available still

Newtonsoft.Json.JsonSerializationException: 'Error converting value "validating" to type 'WorkOS.DirectoryState'.

Looks like the .net sdk is missing a few states in the DirectoryState enum

From workos-dotnet

    public enum DirectoryState
    {
        [EnumMember(Value = "linked")]
        Active,

        [EnumMember(Value = "unlinked")]
        Inactive,

        [EnumMember(Value = "invalid_credentials")]
        InvalidCredentials,
    }

From workos-node

 export type DirectoryState =
  | 'active'
  | 'deleting'
  | 'inactive'
  | 'invalid_credentials'
  | 'validating';