<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Teams Toolkit on Thomy Gölles</title><link>https://thomygoelles.com/tags/teams-toolkit/</link><description>Recent content in Teams Toolkit on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 03 Feb 2024 17:08:46 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/teams-toolkit/index.xml" rel="self" type="application/rss+xml"/><item><title>TeamsFx: Visual Studio project name too long for manifest validation</title><link>https://thomygoelles.com/teamsfx-visual-studio-project-name-too-long-for-manifest-validation/</link><pubDate>Sat, 03 Feb 2024 15:26:38 +0000</pubDate><guid>https://thomygoelles.com/teamsfx-visual-studio-project-name-too-long-for-manifest-validation/</guid><description>&lt;p&gt;When you are working with the Teams Toolkit for Visual Studio and you are using a long project name, you might run into an issue when you want to package your application for deployment. The error message is helpful if you already have some experience with the Teams manifest, but it might be confusing for new developers. The error message we are discussing today is: (×) Error: /name/short must NOT have more than 30 characters&lt;/p&gt;</description></item><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><item><title>Getting started with the Microsoft Teams Framework (TeamsFx)</title><link>https://thomygoelles.com/getting-started-with-the-microsoft-teams-framework-teamsfx/</link><pubDate>Thu, 16 Sep 2021 21:17:41 +0000</pubDate><guid>https://thomygoelles.com/getting-started-with-the-microsoft-teams-framework-teamsfx/</guid><description>&lt;p&gt;A couple of months back, Microsoft started talking about a new way to create applications for Microsoft Teams. Those efforts got different names and with previous and betas and all their different names, it&amp;rsquo;s probably best to quote the current introduction from the actual &lt;a href="https://github.com/OfficeDev/TeamsFx" target="_blank" rel="noopener"&gt;GitHub repo&lt;/a&gt; of the project.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;Microsoft Teams Framework is a library encapsulating common functionality and integration patterns (like simplified access to Microsoft Identity) for developers building apps for Microsoft Teams. The Teams Developer Platform offers a collection of solutions for Teams developers:&lt;/em&gt;&lt;/p&gt;</description></item></channel></rss>