The Calls & Meetings API is now the Microsoft Graph Communications API, SDK package names updated
As the newest API and SDK pair for performing programmatic actions on Microsoft Teams calls makes its way from Public Preview to Generally Available, there are some changes happening to bring it more into line with the other Graph APIs.
Firstly, it has a new name. I much prefer this one, it’s more succinct and abstract, and means that when new features are added that aren’t specific to calls or meetings, it won’t look strange.
There are some other changes as well. These might well be breaking changesto existing applications, or if they aren’t, there will still be things you should do.
NuGet Package names have changed
That’s right – the way you get the SDK has changed. These are the new package names you should use:
The previous versions have been marked with the [Obselete] decorator, meaning that if you continue to use them, they will work…but you’ll receive a warning: Compiler Warning (level 2)CS0618.
Namespace names have changed
There have also been some changes to Namespaces. For instance, the IStatefulClient is now ICommunicationsClient. This will likely involve some rework to your code:
(Some) Attributes and Method Names have changed
Again, likely to break your code on an update. These changes are mostly cosmetic and bring the naming standards in line with the rest of Graph:
no longer used
no longer used
Where to get this new SDK from?
The right place to download this SDK and all its sub-parts isNuGet. If you’re not familiar with it, NuGet is a nice easy way to load in external references to your code. There’s no MSI to install and you can control everything from within Visual Studio.