So far, our SDK for .NET was only targeting .NET Framework, limiting where developers could deploy. This limitation is now a thing of the past, as a public beta of our new SDKs for ย .NET Standard 2.0 and .NET Framework 4.6.1 have been published !

An SDK respecting the specifications of .NET Standard 2.0 โ€ฆ ๐Ÿ“ˆ

The new SDK for .NET comes with a library which is respecting .NET Standard 2.0. This means you can use it with any project running .NET (assuming your project is also compatible with .NET Standard 2.0) from .NET Core and .NET Framework to an integration in your Xamarin iOS or Android app or Unity project. For more information on the compatibility of .NET Standard 2.0, please see to the Microsoft documentation. ๐Ÿ“–

Because .NET Standard is compatible with such a wide range of devices and platforms, we let developers implement their own platform-specific ย audio I/O for this SDK. This means that it is up to the developer to implement this element to access the microphone(s) and loudspeaker(s) of the device the SDK is running on. ๐ŸŽค

Does this mean you are going to have to do an extra work to implement the audio I/O in our .NET Framework applications ?!. ๐Ÿ˜Ÿ

Well, not necessarily ! See below ! ๐Ÿ‘‡

An SDK which is still tailored for .NET Framework 4.6.1 ! ๐Ÿ˜Œ

As we are already providing an SDK for .NET Framework, we couldnโ€™t simply remove it. But because we are now providing the .NET Standard version we canโ€™t also maintain two code base at the same time.

To solve this issue, the main class of our .NET Framework SDK is now extending the main class of our .NET Standard, making the code base easier to maintain. This brings one requirement though, developers using SDK for .NET Framework will have to link their project to the Chirp .NET Standard library too - luckily this is not too hard to do. ๐Ÿ˜‰

Also, as in the previous version, the SDK for .NET Framework still handles audio I/O. For developers who were already using the SDK, it means no changes at all from an external point of view. For Chirp, it means a lot of refactoring, but a cleaner and easier code to maintain, which means everybody is winning. ๐Ÿ’ช

Stay tuned for a possible new SDK ๐Ÿ‘€

The arrival of a Chirp SDK for .NET Standard 2.0 brings hope to welcome a new SDK, which is nothing less than full UWP support. This SDK has been in Chirpโ€™s internal library for a long time without being publicly available, and has been hard to maintain. Chirp for .NET Standard 2.0 could have been the last push we needed to provide a proper UWP SDK publicly. ๐Ÿฃ

NB : About the Chirp .NET SDKs, they are currently a beta version which means any feedback or bug report will be very much appreciated. If you have any feedback, contact us. ๐Ÿ“ง