<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SDK V5 on Thomy Gölles</title><link>https://thomygoelles.com/tags/sdk-v5/</link><description>Recent content in SDK V5 on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 24 Mar 2023 15:29:18 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/sdk-v5/index.xml" rel="self" type="application/rss+xml"/><item><title>TeamsFx: How to use Microsoft Graph SDK v5 already</title><link>https://thomygoelles.com/teamsfx-graph-sdk-v5/</link><pubDate>Wed, 22 Mar 2023 12:58:35 +0000</pubDate><guid>https://thomygoelles.com/teamsfx-graph-sdk-v5/</guid><description>&lt;p&gt;Looking at the latest release from the Microsoft Graph SDK team an their version 5.0.0 for dotnet three weeks ago, I was wondering how to use it with TeamsFx. I was not able to find any documentation on this topic, so I decided to write this post to share my findings.&lt;/p&gt;
&lt;h2 id="what-is-the-microsoft-graph-sdk-v5-for-dotnet"&gt;What is the Microsoft Graph SDK v5 for dotnet?&lt;/h2&gt;
&lt;p&gt;Using the Microsoft Graph .NET SDK, you can take advantage of a fluent API and models that support retry handling, secure redirects, batching requests, large file management, and many more capabilities. This allows you to focus on what really matters in your Teams application instead of having to worry about the details of the HTTP requests and responses.&lt;/p&gt;</description></item></channel></rss>