nanoFramework.M5StickCPlus 1.0.1-preview.64

Prefix Reserved
This is a prerelease version of nanoFramework.M5StickCPlus.
There is a newer version of this package available.
See the version list below for details.
dotnet add package nanoFramework.M5StickCPlus --version 1.0.1-preview.64
                    
NuGet\Install-Package nanoFramework.M5StickCPlus -Version 1.0.1-preview.64
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="nanoFramework.M5StickCPlus" Version="1.0.1-preview.64" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="nanoFramework.M5StickCPlus" Version="1.0.1-preview.64" />
                    
Directory.Packages.props
<PackageReference Include="nanoFramework.M5StickCPlus" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add nanoFramework.M5StickCPlus --version 1.0.1-preview.64
                    
#r "nuget: nanoFramework.M5StickCPlus, 1.0.1-preview.64"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package nanoFramework.M5StickCPlus@1.0.1-preview.64
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=nanoFramework.M5StickCPlus&version=1.0.1-preview.64&prerelease
                    
Install as a Cake Addin
#tool nuget:?package=nanoFramework.M5StickCPlus&version=1.0.1-preview.64&prerelease
                    
Install as a Cake Tool

Quality Gate Status Reliability Rating License NuGet #yourfirstpr Discord

nanoFramework logo


Welcome to the .NET nanoFramework M5Stack Libraries repository

Build status

Component Build Status NuGet Package
nanoFramework.M5Core Build Status NuGet
nanoFramework.M5Core (preview) Build Status NuGet
nanoFramework.M5Stick Build Status NuGet
nanoFramework.M5Stick (preview) Build Status NuGet
nanoFramework.M5StickCPlus Build Status NuGet
nanoFramework.M5StickCPlus (preview) Build Status NuGet
nanoFramework.M5Core2 Build Status NuGet
nanoFramework.M5Core2 (preview) Build Status NuGet
nanoFramework.Fire Build Status NuGet
nanoFramework.Fire (preview) Build Status NuGet
nanoFramework.AtomLite Build Status NuGet
nanoFramework.AtomLite (preview) Build Status NuGet
nanoFramework.AtomMatrix Build Status NuGet
nanoFramework.AtomMatrix (preview) Build Status NuGet

Usage

These NuGet packages provide a support for M5Stack products:

Note 1: Before trying to add NuGet packages to your projects and/or before flashing the devices (see next section) using MS Visual Studio (VS), open VS > Tools > Options > NuGet Package Manager > Package Sources and make sure that it contains an entry pointing to https://api.nuget.org/v3/index.json , otherwise add it. Note 2: When invoking VS > Project > Manage NuGet Packages make sure that in the Package source drop-down menu (right upper corner) "nuget.org" is selected. Also if you're using preview version the "include prerelease" checkbox should be clicked/selected as well.

The NuGets bring support for the screens as well and require to be flashed with the proper image (using nanoff dotnet CLI). On the examples below replace COM3 with the appropriate number of the COM port to which your device is connected. (on Windows you can check this in the Device Manager).

For the M5Core:

nanoff --target M5Core --update --preview --serialport COM3

For the M5StickC:

nanoff --target M5StickC --update --preview --serialport COM3 --baud 115200

For the M5StickCPlus:

nanoff --target M5StickCPlus --update --preview --serialport COM3

For the M5Core2 and Fire:

nanoff --target M5Core2 --update --preview --serialport COM3

For the Atom Lite and Matrix:

nanoff --target ESP32_PICO --update --preview --serialport COM3

Note 3: If the nanoff commands fails, make sure you have followed instruction from Note 1 above.

Once you have the NuGets, you can then enjoy accessing the screen, the accelerometer, get a Grove I2C connecter, add events on the buttons. And you don't even need to think about anything, all is done for you in the most transparent way!

Note 4: All the classes that you'll have access are all using the Lazy pattern to be instantiated including the screen. This have the advantage to use as little memory and setup time as possible.

In the samples below, we'll use either M5Core or M5Stick as examples, they are all working in a very similar way.

Namespaces

Make sure you add the proper namespaces reference to your C# program header e.g. using nanoFramework;

Screen

The only thing you need to do to access the screen is to initialize it (please note that InitializeScreen() it's target specific) e.g.:

For Core:

M5Core.InitializeScreen();

For StickCPlus:

M5StickCPlus.InitializeScreen();

Once you've initialized it, you can access both a Screen static class and a Console static class.

THe Screen one brings primitives to write directly on the screen points or scare of colours as well as writing a text.

For example, you can write a blue square of 10x10 at the position 0, 0 like this:

ushort[] toSend = new ushort[100];
ushort blue = ColorUtility.To16Bpp(Color.Blue);

for (int i = 0; i < toSend.Length; i++)
{
    toSend[i] = blue;
}

Screen.Write(0, 0, 10, 10, toSend);

The Console class works in a similar way as the classic System.Console. In order to use it you have to reference it using the fully qualified name of the methods, like this:

nanoFramework.Console.Clear();

// Test the console display
nanoFramework.Console.Write("This is a short text. ");
nanoFramework.Console.ForegroundColor = nanoFramework.Presentation.Media.Color.Red;
nanoFramework.Console.WriteLine("This one displays in red after the previous one and is already at the next line.");
nanoFramework.Console.BackgroundColor = nanoFramework.Presentation.Media.Color.Yellow;
nanoFramework.Console.ForegroundColor = nanoFramework.Presentation.Media.Color.RoyalBlue;
nanoFramework.Console.WriteLine("And this is blue on yellow background");
nanoFramework.Console.ResetColor();
nanoFramework.Console.CursorLeft = 0;
nanoFramework.Console.CursorTop = 8;
nanoFramework.Console.Write("This is white on black again and on 9th line");

Note: You can change the default font as well, you need to provide it as a property. The Cursor positions are calculated with the largest possible character.

M5Core2 and Fire have SPRAM, so you can get a full screen buffer as well. Refer to the Graphics samples to understand all you can do with it.

Buttons

The main buttons except the power buttons are exposed.

On the M5Stack and Fire they are called ButtonLeft, ButtonCenter and ButtonRight. You can get access to the events as well. For example:

M5Stack.ButtonLeft.Press += (sender, e) =>
{
    Console.ForegroundColor = Color.Yellow;
    Console.CursorLeft = 0;
    Console.CursorTop = 0;
    Console.Write($"Left Pressed  ");
};

On the M5StickC/CPlus they are called ButtonM5 and ButtonRight. You can get access to the status of the button, the events and everything you need. For example:

while (!M5StickC.ButtonRight.IsPressed)
{
    Thread.Sleep(10);
}

M5StickC.M5Button.IsHoldingEnabled = true;
M5StickC.M5Button.Holding += (sender, e) =>
{
    Console.Write("M5 button hold long.");
};

On the Atom Lite/Matrix it's called Button. You can get access to the status of the button, the events and everything you need. For example:

AtomLite.Button.Press +=> (sender, e)
{
    var color = AtomLite.NeoPixel.GetColor();
    if(color.R > 0)
    {
        AtomLite.NeoPixel.SetColor(Color.FromArgb(255, 0, 255, 0));
    }
    else if (color.G > 0)
    {
        AtomLite.NeoPixel.SetColor(Color.FromArgb(255, 0, 0, 255));
    }
    else
    {
        AtomLite.NeoPixel.SetColor(Color.FromArgb(255, 255, 0, 0));
    }
};

Note: The M5Core2 has touch screen and the buttons are "virtual"". See next section to see how to use them.

M5Core2 touch panel and buttons

The touch panel comes with the screen. Both are initialized and activated at the same time. To get the touch events, you'll have to register to the TouchEvent event:

M5Core2.InitializeScreen();
M5Core2.TouchEvent += TouchEventCallback;

Here is an example on how to check if you are on a button or not and get the various elements:

void TouchEventCallback(object sender, TouchEventArgs e)
{
    const string StrLB = "LEFT BUTTON PRESSED  ";
    const string StrMB = "MIDDLE BUTTON PRESSED  ";
    const string StrRB = "RIGHT BUTTON PRESSED  ";
    const string StrXY1 = "TOUCHED at X= ";
    const string StrXY2 = ",Y= ";
    const string StrID = ",Id= ";
    const string StrDoubleTouch = "Double touch. ";
    const string StrMove = "Moving... ";
    const string StrLiftUp = "Lift up. ";

    Debug.WriteLine($"Touch Panel Event Received Category= {e.EventCategory} Subcategory= {e.TouchEventCategory}");
    Console.CursorLeft = 0;
    Console.CursorTop = 0;

    Debug.WriteLine(StrXY1 + e.X + StrXY2 + e.Y + StrID + e.Id);
    Console.WriteLine(StrXY1 + e.X + StrXY2 + e.Y + StrID + e.Id + "  ");

    if ((e.TouchEventCategory & TouchEventCategory.LeftButton) == TouchEventCategory.LeftButton)
    {
        Debug.WriteLine(StrLB);
        Console.WriteLine(StrLB);
    }
    else if ((e.TouchEventCategory & TouchEventCategory.MiddleButton) == TouchEventCategory.MiddleButton)
    {
        Debug.WriteLine(StrMB);
        Console.WriteLine(StrMB);
    }
    else if ((e.TouchEventCategory & TouchEventCategory.RightButton) == TouchEventCategory.RightButton)
    {
        Debug.WriteLine(StrRB);
        Console.WriteLine(StrRB);
    }

    if ((e.TouchEventCategory & TouchEventCategory.Moving) == TouchEventCategory.Moving)
    {
        Debug.WriteLine(StrMove);
        Console.Write(StrMove);
    }

    if ((e.TouchEventCategory & TouchEventCategory.LiftUp) == TouchEventCategory.LiftUp)
    {
        Debug.WriteLine(StrLiftUp);
        Console.Write(StrLiftUp);
    }

    if ((e.TouchEventCategory & TouchEventCategory.DoubleTouch) == TouchEventCategory.DoubleTouch)
    {
        Debug.WriteLine(StrDoubleTouch);
        Console.Write(StrDoubleTouch);
    }

    Console.WriteLine("                                    ");
    Console.WriteLine("                                    ");
    Console.WriteLine("                                    ");
}

The TouchEventCategory enum is a flag and can combine buttons and states. The buttons are mutually exclusive, so you can only have the Left, Middle or Right button, the states are Moving and LiftUp. Moving is happening when a contact has already been made and the touch point is moving. LiftUp will appear when the contact is released.

DoubleTouch is a specific that let you know there is another contact point happening. Each contact point will receive this flag. The event will be raised 2 times, one for each point. In a double touch context, you may not get the second point LiftUp event but you'll get the change with the disappearance of the DoubleTouch flag and the final LiftUp on the first point.

Power management

The M5Core and M5StickC/CPlus are exposing their power management elements. It is not recommended to change any default value except if you know what you are doing.

Please refer to the detailed examples for the AXP192 used in the M5StickC/CPlus; M5Core2 and IP5306 for the M5Core and Fire.

Accelerometer and Gyroscope

You can get access to the Accelerometer and Gyroscope like this:

var ag = M5Core.AccelerometerGyroscope;
// Do not move the M5Core/M5Stick during the calibration
ag.Calibrate(100);
var acc = ag.GetAccelerometer();
var gyr = ag.GetGyroscope();
Debug.WriteLine($"Accelerometer data x:{acc.X} y:{acc.Y} z:{acc.Z}");
Debug.WriteLine($"Gyroscope data x:{gyr.X} y:{gyr.Y} z:{gyr.Z}\n");

Refer to the MPU6886 documentation for more detailed usage on this sensor.

Magnetometer

The M5Core has a magnetometer, you can access it as well:

var mag = M5Core.Magnetometer;
// It is more than strongly recommended to calibrate the magnetometer.
// Move the M5Core in all directions to have a proper calibration.
mag.CalibrateMagnetometer(100);
var magVal = mag.ReadMagnetometer();
Console.WriteLine($"x={magVal.X:N2}   ");
Console.WriteLine($"y={magVal.Y:N2}   ");
Console.WriteLine($"Z={magVal.Z:N2}   ");
var headDir = Math.Atan2(magVal.X, magVal.Y) * 180.0 / Math.PI;
Console.WriteLine($"h={headDir:N2}  ");

SerialPort

The M5Core and M5Core2 can provide a Serial Port, just get it like this:

// You can access any of the Serial Port feature
M5Core.SerialPort.Open(115200);
// Do anything else you need
M5Core.SerialPort.Close();

Refer to the SerialPort documentation for more information.

ADC Channels

ADC Channels are pre setup on the M5Core, M5Core2, Fire and Atom Lite/Matrix, access them like this:

// This will give you the ADC1 channel 7 which is on pin 35 of M5Core
AdcChannel myChannel = M5Core.GetAdcGpio(35);

Refer to the M5Stack documentation to have the mapping of the ADC channels and the pins.

I2C Device/Grove

You can get an I2cDevice/Grove like this:

// In this example, the I2C address of the device is 0x42:
I2cDevice myDevice = M5Core.GetGrove(0x42);
// replacing GetGrove by GetI2cDevice will have the same impact

SPI Device

The M5Core, M5Core2, Fire and Atom Lite/Matrix provides as well an SpiDevice:

// In this case GPIO5 will be used as chip select:
SpiDevice mySpi = M5Core.GetSpiDevice(5);

GPIO Controller

Similar as previously, you can get the GpioController on any of the M5Core, M5Core2, Fire and M5StickC/CPlus:

// This will open the GPIO 36 as output
var pin5 = M5StickC.GpioController.OpenPin(36, PinMode.Output);

DAC

The M5Core, M5Core2, Fire and Atom Lite/Matrix exposes 2 DAC and you can access them thru the Dac1 and Dac2 properties. Refer to the DAC documentation for more information.

Led

The M5StickC/CPlus exposes a led. You can access it thru the Led property:

// This will toggle the led:
M5StickC.Led.Toggle();

Infrared Led

The M5StickC/CPlus and Atom Lite/Matrix exposes an infrared led. You can access it thru the InfraredLed property. This will give you a TransmitterChannel. Check out the sample pack to understand how to use it.

NeoPixel

The Atom Lite exposes a rgb led. You can access it thru the NeoPixel property:

// This will set NeoPixel to green:
AtomLite.NeoPixel.SetColor(Color.Green);

RGB LED matrix

The Atom Matrix has a matrix of 25 RGB LEDs. The position of the LEDs in the array follows their placement in the matrix, being 0 the one at the top left corner, growing left to right, top to bottom.

You can access it thru the LedMatrix property, like this:

// This will set the RGB LED at position 0 to green
AtomMatrix.LedMatrix.SetColor(0, Color.Green);

After you're done with updating all the LEDs that you want to change, flush the updated to the LEDs, like this:

// This will update all RGB LED 
AtomMatrix.LedMatrix.Update();

Feedback and documentation

For documentation, providing feedback, issues and finding out how to contribute please refer to the Home repo.

Join our Discord community here.

Credits

The list of contributors to this project can be found at CONTRIBUTORS.

License

The nanoFramework Class Libraries are licensed under the MIT license.

Code of Conduct

This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behaviour in our community. For more information see the .NET Foundation Code of Conduct.

.NET Foundation

This project is supported by the .NET Foundation.

Product Compatible and additional computed target framework versions.
.NET Framework net is compatible. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
1.1.281 116 7/28/2025
1.1.280 222 4/28/2025
1.1.279 207 4/7/2025
1.1.278 206 4/2/2025
1.1.277 224 4/2/2025
1.1.276 226 3/12/2025
1.1.275 223 3/10/2025
1.1.274 283 3/5/2025
1.1.273 208 3/3/2025
1.1.272 155 2/27/2025
1.1.271 153 2/27/2025
1.1.270 151 2/27/2025
1.1.269 159 2/26/2025
1.1.268 149 2/26/2025
1.1.267 147 2/25/2025
1.1.266 165 2/25/2025
1.1.265 170 2/10/2025
1.1.264 169 2/5/2025
1.1.263 156 2/4/2025
1.1.262 160 2/4/2025
1.1.261 155 2/4/2025
1.1.260 158 2/3/2025
1.1.259 176 1/31/2025
1.1.255 164 1/20/2025
1.1.253 169 12/30/2024
1.1.252 163 12/23/2024
1.1.249 168 12/16/2024
1.1.248 156 12/16/2024
1.1.247 158 12/4/2024
1.1.246 186 10/31/2024
1.1.245 191 10/18/2024
1.1.244 154 10/16/2024
1.1.243 163 10/12/2024
1.1.242 172 10/11/2024
1.1.241 169 10/4/2024
1.1.240 162 10/2/2024
1.1.239 166 9/27/2024
1.1.238 190 9/6/2024
1.1.236 168 8/30/2024
1.1.235 164 8/28/2024
1.1.234 190 8/16/2024
1.1.232 135 7/31/2024
1.1.229 173 7/19/2024
1.1.228 149 7/17/2024
1.1.227 145 7/12/2024
1.1.225 185 6/28/2024
1.1.223 184 6/19/2024
1.1.220 176 5/31/2024
1.1.217 187 5/15/2024
1.1.215 186 5/10/2024
1.1.213 179 4/17/2024
1.1.211 170 4/15/2024
1.1.209 187 4/5/2024
1.1.207 174 3/27/2024
1.1.203 195 2/28/2024
1.1.201 199 1/31/2024
1.1.199 171 1/26/2024
1.1.197 175 1/24/2024
1.1.187 249 11/17/2023
1.1.185 155 11/14/2023
1.1.183 171 11/9/2023
1.1.180 150 11/8/2023
1.1.177 188 10/11/2023
1.1.175 176 9/29/2023
1.1.171 204 9/8/2023
1.1.169 221 9/6/2023
1.1.167 200 8/18/2023
1.1.163 216 8/2/2023
1.1.161 205 7/28/2023
1.1.157 208 7/19/2023
1.1.155 218 7/14/2023
1.1.152 208 6/21/2023
1.1.150 218 6/14/2023
1.1.148 216 6/7/2023
1.1.146 218 5/31/2023
1.1.144 220 5/24/2023
1.1.142 245 5/17/2023
1.1.139 249 5/11/2023
1.1.137 239 5/5/2023
1.1.135 298 4/5/2023
1.1.133 313 3/29/2023
1.1.131 302 3/24/2023
1.1.128 311 3/17/2023
1.1.125 298 3/16/2023
1.1.123 292 3/13/2023
1.1.121 322 3/9/2023
1.1.119 339 2/27/2023
1.1.117 329 2/27/2023
1.1.115 346 2/22/2023
1.1.113 328 2/20/2023
1.1.111 321 2/16/2023
1.1.106 405 1/10/2023
1.1.104 391 1/9/2023
1.1.102 380 1/6/2023
1.1.100 377 1/6/2023
1.1.98 401 1/5/2023
1.1.96 384 12/29/2022
1.1.90 423 11/15/2022
1.1.88 424 11/14/2022
1.1.86 441 11/5/2022
1.1.84 466 11/5/2022
1.1.82 440 11/4/2022
1.1.80 440 11/3/2022
1.1.78 449 11/1/2022
1.1.76 467 10/27/2022
1.1.70 518 10/13/2022
1.1.68 495 10/12/2022
1.1.64 509 10/7/2022
1.1.62 467 10/7/2022
1.1.58 569 9/23/2022
1.1.55 575 9/23/2022
1.1.53 551 9/22/2022
1.1.47 515 9/21/2022
1.1.45 535 9/16/2022
1.1.42 533 9/15/2022
1.1.40 554 9/8/2022
1.1.38 527 9/7/2022
1.1.36 516 9/3/2022
1.1.34 522 8/15/2022
1.1.32 544 8/6/2022
1.1.30 523 8/5/2022
1.1.28 506 8/4/2022
1.1.26 542 8/3/2022
1.1.24 526 8/3/2022
1.1.22 533 8/2/2022
1.1.20 549 7/30/2022
1.1.18 545 7/26/2022
1.1.16 530 7/24/2022
1.1.14 540 7/23/2022
1.1.12 571 7/13/2022
1.1.7 588 7/7/2022
1.1.5 563 7/7/2022
1.1.3 572 7/6/2022
1.1.1 550 7/5/2022
1.0.107.13280 553 7/1/2022
1.0.105.49254 559 6/30/2022
1.0.102.851 549 6/28/2022
1.0.100.17145 542 6/28/2022
1.0.98.48733 550 6/28/2022
1.0.96.40373 554 6/26/2022
1.0.92.59206 558 6/24/2022
1.0.90.38187 539 6/16/2022
1.0.88.50207 523 6/15/2022
1.0.86.52668 539 6/14/2022
1.0.83.14512 535 6/13/2022
1.0.81.41619 558 6/8/2022
1.0.79.53990 549 6/3/2022
1.0.77.26764 559 6/3/2022
1.0.75.37268 565 6/1/2022
1.0.72.43325 533 5/31/2022
1.0.70.15497 541 5/31/2022
1.0.68.55953 576 5/31/2022
1.0.66.24331 572 5/27/2022
1.0.64.6330 542 5/26/2022
1.0.62.28047 531 5/26/2022
1.0.60.49583 547 5/25/2022
1.0.58.20063 564 5/24/2022
1.0.56.35800 532 5/23/2022
1.0.54.60782 540 5/20/2022
1.0.51.48271 567 5/12/2022
1.0.49.30985 539 5/6/2022
1.0.46 567 5/5/2022
1.0.42 577 4/26/2022
1.0.40 546 4/25/2022
1.0.38 543 4/24/2022
1.0.36 547 4/23/2022
1.0.34 540 4/22/2022
1.0.32 573 4/22/2022
1.0.30 568 4/21/2022
1.0.26 591 4/21/2022
1.0.24 584 4/20/2022
1.0.22 552 4/19/2022
1.0.20 574 4/18/2022
1.0.18 569 4/17/2022
1.0.16 583 4/16/2022
1.0.14 568 4/15/2022
1.0.12 559 4/13/2022
1.0.10 547 4/6/2022
1.0.8 554 4/4/2022
1.0.6 541 4/3/2022
1.0.4 562 3/31/2022
1.0.2 557 3/31/2022
1.0.1-preview.68 212 3/30/2022
1.0.1-preview.67 213 3/25/2022
1.0.1-preview.66 223 3/25/2022
1.0.1-preview.65 220 3/25/2022
1.0.1-preview.64 206 3/23/2022
1.0.1-preview.63 197 3/22/2022
1.0.1-preview.62 200 3/21/2022
1.0.1-preview.61 213 3/20/2022
1.0.1-preview.60 215 3/19/2022
1.0.1-preview.58 219 3/16/2022
1.0.1-preview.57 222 3/16/2022
1.0.1-preview.56 213 3/14/2022
1.0.1-preview.55 217 3/14/2022
1.0.1-preview.54 218 3/11/2022
1.0.1-preview.53 212 3/9/2022
1.0.1-preview.52 224 3/8/2022
1.0.1-preview.51 215 3/7/2022
1.0.1-preview.50 202 3/4/2022
1.0.1-preview.49 208 3/3/2022
1.0.1-preview.48 210 2/27/2022
1.0.1-preview.47 209 2/26/2022
1.0.1-preview.46 203 2/25/2022
1.0.1-preview.45 215 2/18/2022
1.0.1-preview.43 211 2/16/2022
1.0.1-preview.42 229 2/12/2022
1.0.1-preview.41 210 2/10/2022
1.0.1-preview.40 220 2/9/2022
1.0.1-preview.39 227 2/8/2022
1.0.1-preview.38 224 2/6/2022
1.0.1-preview.37 240 2/5/2022
1.0.1-preview.36 238 2/4/2022
1.0.1-preview.35 226 2/3/2022
1.0.1-preview.34 243 1/31/2022
1.0.1-preview.32 233 1/31/2022
1.0.1-preview.31 236 1/29/2022
1.0.1-preview.30 228 1/28/2022
1.0.1-preview.28 226 1/28/2022
1.0.1-preview.26 228 1/27/2022
1.0.1-preview.25 225 1/27/2022
1.0.1-preview.24 220 1/26/2022
1.0.1-preview.23 224 1/24/2022
1.0.1-preview.22 224 1/21/2022
1.0.1-preview.21 228 1/21/2022
1.0.1-preview.20 230 1/21/2022
1.0.1-preview.19 224 1/21/2022
1.0.1-preview.18 224 1/20/2022
1.0.1-preview.17 237 1/20/2022
1.0.1-preview.16 239 1/16/2022
1.0.1-preview.15 236 1/14/2022
1.0.1-preview.14 238 1/14/2022
1.0.1-preview.13 231 1/12/2022
1.0.1-preview.12 233 1/11/2022
1.0.1-preview.9 236 1/5/2022
1.0.1-preview.8 231 12/31/2021
1.0.1-preview.7 222 12/31/2021
1.0.1-preview.6 234 12/29/2021
1.0.1-preview.5 239 12/28/2021
1.0.1-preview.3 251 12/27/2021
1.0.0 443 12/23/2021
1.0.0-preview.99 237 12/23/2021
1.0.0-preview.98 248 12/23/2021
1.0.0-preview.94 284 11/12/2021
1.0.0-preview.91 260 11/9/2021
1.0.0-preview.88 267 11/9/2021
1.0.0-preview.86 263 11/3/2021
1.0.0-preview.83 304 10/28/2021
1.0.0-preview.81 289 10/27/2021