<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Development on Thomy Gölles</title><link>https://thomygoelles.com/tags/development/</link><description>Recent content in Development on Thomy Gölles</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 03 Mar 2022 06:00:00 +0000</lastBuildDate><atom:link href="https://thomygoelles.com/tags/development/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Teams Framework (TeamsFx) - Infographic</title><link>https://thomygoelles.com/teamsfx-infographic/</link><pubDate>Thu, 03 Mar 2022 06:00:00 +0000</pubDate><guid>https://thomygoelles.com/teamsfx-infographic/</guid><description>&lt;p&gt;Spending some time talking with customers and fellow developers about TeamsFx made me realise, that there is some
confusion about how Microsoft named different parts of the framework. I created this one slide to explain the different flavours, names and ideas behind TeamsFx in my sessions. As sharing is caring, here we go!&lt;/p&gt;
&lt;p&gt;&lt;img src="https://thomygoelles.com/img/2022/04/TeamsFXNet01.png" alt="TeamsFx Infographic"&gt;&lt;/p&gt;</description></item><item><title>TeamsFx - add custom debug profiles</title><link>https://thomygoelles.com/teamsfx-add-custom-debug-profiles/</link><pubDate>Tue, 19 Oct 2021 22:49:50 +0000</pubDate><guid>https://thomygoelles.com/teamsfx-add-custom-debug-profiles/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Today&amp;rsquo;s post is about the need(pain?) of installing your Teams application at the start of every TeamsFx debugging session. If you are new to TeamsFx in Visual Studio please read this &lt;a href="https://thomygoelles.com/getting-started-with-the-microsoft-teams-framework-teamsfx/"&gt;intro&lt;/a&gt; first as for the next parts we assume that you already familiarized yourself with the toolkit and its features.&lt;/p&gt;
&lt;p&gt;There are very good reasons why the Teams Toolkit always starts with the app install screen. At that screen, you can choose where to deploy your app. You can see the current version of your app and all other details of the manifest. But if you are in &amp;ldquo;the zone&amp;rdquo;, you might wish that there is a way to get to your latest changes just a bit quicker. What we will be talking about here won&amp;rsquo;t apply to every possible Teams app, but it works for tabs. To be precise, it works for everything you can create a Teams deep link for.&lt;/p&gt;</description></item><item><title>TeamsFx and .NET Hot Reload</title><link>https://thomygoelles.com/teamsfx-and-net-hot-reload/</link><pubDate>Sat, 02 Oct 2021 23:00:25 +0000</pubDate><guid>https://thomygoelles.com/teamsfx-and-net-hot-reload/</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;If you follow the news around .NET 6 and Visual Studio 2022 one of the most time-saving features for developers might be the .NET Hot Reload experience for editing code at runtime. This feature is part of the .NET 6 release and will be available across various project types such as WPF, Windows Forms, .NET MAUI, ASP.NET Core apps code-behind, Console applications, WinUI3 and many others. &lt;a href="https://devblogs.microsoft.com/dotnet/introducing-net-hot-reload/" target="_blank" rel="noopener"&gt;[1]&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devblogs.microsoft.com/dotnet/wp-content/uploads/sites/10/2021/05/dotnet-Hot-Reload-VS-2019-version-16_11.gif" alt=""&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Hot Reload example from &lt;a href="https://devblogs.microsoft.com/dotnet/introducing-net-hot-reload/" target="_blank" rel="noopener"&gt;Introducing the .NET Hot Reload experience for editing code at runtime - .NET Blog (microsoft.com)&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Create a Microsoft Teams Tab with Blazor</title><link>https://thomygoelles.com/microsoft-teams-tab-with-blazor/</link><pubDate>Thu, 04 Jun 2020 22:08:24 +0000</pubDate><guid>https://thomygoelles.com/microsoft-teams-tab-with-blazor/</guid><description>&lt;p&gt;This post highlights how you can use ASP.NET Blazor Server Side to host your Microsoft Teams tabs. The link to Teams can be achieved by leveraging the Teams JavaScript API, authentication is provided through ADAL.JS. As soon as we get our access token to the Microsoft Graph, we can call endpoints in native C# and visualize the data in Razor components. On both ends in Blazor, UI and data, you can reuse your C# skills or your existing business logic libraries to bring those to Microsoft Teams as a tab.&lt;/p&gt;</description></item><item><title>SPFx Development in WSL 2.0 - Linux files integration in Explorer</title><link>https://thomygoelles.com/spfx-development-in-wsl-2-0-linux-files-integration-in-explorer/</link><pubDate>Sun, 19 Apr 2020 22:50:16 +0000</pubDate><guid>https://thomygoelles.com/spfx-development-in-wsl-2-0-linux-files-integration-in-explorer/</guid><description>&lt;p&gt;Last week on Thursday my Windows PC got the latest Windows Preview Build. I was looking for a new version of the preview as the last one broke my webcams for Microsoft Teams. In times like these, not having a working video feed in Teams is not really a situation you want to end up with. There was a workaround to use OBS and a virtual camera to get it working but this was far from stable so I searched for a different way.&lt;/p&gt;</description></item><item><title>SharePoint look book: how to provision templates to non-English tenants</title><link>https://thomygoelles.com/sharepoint-look-book-templates-on-a-non-english-tenant/</link><pubDate>Mon, 18 Nov 2019 23:08:19 +0000</pubDate><guid>https://thomygoelles.com/sharepoint-look-book-templates-on-a-non-english-tenant/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Over the last weeks since Ignite 2019, the &lt;a href="https://lookbook.microsoft.com/" target="_blank" rel="noopener"&gt;SharePoint look book&lt;/a&gt; got more and more attention. Microsoft showcases beautiful designs on the look book page, and with the help of the SharePoint provisioning service, you can deploy those designs within a few clicks from an admin user.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://thomygoelles.com/img/2019/11/image.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;This is an excellent feature and allows you to deploy lovely demo site collections within minutes. That would be all great unless someone made a significant mistake during the creation of your tenant. In my case, that was me.&lt;/p&gt;</description></item><item><title>SelectedTech Webinar 6 - QnAMaker, SharePoint and Microsoft Flow</title><link>https://thomygoelles.com/selectedtech/selectedtech-webinar-6-qnamaker-sharepoint-flow/</link><pubDate>Thu, 08 Aug 2019 10:24:06 +0000</pubDate><guid>https://thomygoelles.com/selectedtech/selectedtech-webinar-6-qnamaker-sharepoint-flow/</guid><description>&lt;p&gt;In episode 6 of our SelectedTech podcast/webinar series, Albert-Jan introduces his concept of updating the QnAMaker knowledge base with data from SharePoint. To make this as easy as possible he used Microsoft Flow already a couple of times at customer demonstrate the use case of bots updated that way. Talking about Flow at this particular time means we also spend some minutes on the latest license news for PowerApps and Flow.&lt;/p&gt;</description></item><item><title>10 things you should do with your Office365 demo or dev tenant</title><link>https://thomygoelles.com/10-things-you-should-do-with-your-dev-demo-tenant/</link><pubDate>Tue, 30 Jul 2019 21:57:12 +0000</pubDate><guid>https://thomygoelles.com/10-things-you-should-do-with-your-dev-demo-tenant/</guid><description>&lt;p&gt;In the last couple of months, I needed to create a few demo or development tenants in Office365. As I don&amp;rsquo;t want to reinvent the wheel all the time, I created a list that steers me through the process and makes sure I don&amp;rsquo;t forget an important step. As you probably know, ticking things off a todo list can be a very satisfying activity. So the next time you need to create a development or demo tenant think of this list, copy it to your todo app and enjoy the good vibes while ticking off the boxes of your own 10 things.&lt;/p&gt;</description></item><item><title>SelectedTech Webinar 3 - CI/CD with your bot and Azure DevOps</title><link>https://thomygoelles.com/selectedtech/selectedtech-webinar-003/</link><pubDate>Wed, 17 Jul 2019 21:34:35 +0000</pubDate><guid>https://thomygoelles.com/selectedtech/selectedtech-webinar-003/</guid><description>&lt;p&gt;The SelectedTech Webinar 003 about using CI/CD with your bot and Azure DevOps is now available. We recorded the session on July 4th 2019. Check it out and leave a comment or send a tweet or message if you have any questions.&lt;/p&gt;
&lt;p&gt;In this episode Stephan demos how to create a build and release pipeline within Azure DevOps. We discuss the two different configurations for build and release and talk about how to reuse your config for different target systems. The goal is to switch your target environment with Azure DevOps and to be able to deploy your bot to different Azure tenants just by clicking through the release pipeline.&lt;/p&gt;</description></item><item><title>SelectedTech Webinar 2 - QnA Bot Local Development</title><link>https://thomygoelles.com/selectedtech/selectedtech-webinar-002/</link><pubDate>Mon, 08 Jul 2019 17:22:22 +0000</pubDate><guid>https://thomygoelles.com/selectedtech/selectedtech-webinar-002/</guid><description>&lt;p&gt;The SelectedTech Webinar 002 about local QnA bot development and deployment to Microsoft Azure and Microsoft Teams is now available. We recorded the session on July 4th 2019. Check it out and leave a comment or send a tweet or message if you have any questions.&lt;/p&gt;
&lt;p&gt;In this episode we take the QnA bot from webinar 001 and download the code to a local machine. After showing how to run the bot in a local IIS we use ngrok for tunneling access for a Teams deployment. After making a minor code change we republish the bot and make sure everything is still working. The episode ends with Rick asking Stephan about using Azure DevOps for CI/CD which will be our topic for Webinar 003.&lt;/p&gt;</description></item><item><title>Microsoft Teams - weiterführende Links</title><link>https://thomygoelles.com/deutsch/teams-de/</link><pubDate>Mon, 17 Jun 2019 11:35:44 +0000</pubDate><guid>https://thomygoelles.com/deutsch/teams-de/</guid><description>&lt;p&gt;Letzte Woche am 14. Juni durfte ich gemeinsam mit Microsoft Österreich einen Workshop zum Thema Zusammenarbeit und Kommunikation in Teams halten. Dabei ist die Idee entstanden sämtliche Ressourcen wie Blog Artikel oder Präsentationen und Hyperlinks die als Grundlage für den Workshop verwendet wurden irgendwo gesammelt zur Verfügung zu stellen. Über die Zeit entseht hier hoffentlich also eine kleine Übersicht mit Infos zu Microsoft Teams.&lt;/p&gt;
&lt;h2 id="einstieg-in-teams"&gt;Einstieg in Teams&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://www.youtube.com/watch?v=s3aQV3T0D6c" target="_blank" rel="noopener"&gt;https://www.youtube.com/watch?v=s3aQV3T0D6c&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Teams Intro&lt;/p&gt;</description></item><item><title>How to sideload an existing SPFx package in Microsoft Teams</title><link>https://thomygoelles.com/how-to-sideload-an-existing-spfx-package-in-microsoft-teams/</link><pubDate>Mon, 12 Nov 2018 00:45:45 +0000</pubDate><guid>https://thomygoelles.com/how-to-sideload-an-existing-spfx-package-in-microsoft-teams/</guid><description>&lt;h4 id="introduction"&gt;Introduction&lt;/h4&gt;
&lt;p&gt;In preparation for a talk next week I spent the whole weekend on creating demos and slides. A couple of days ago the SharePoint team released version 1.7 of the SharePoint Framework. This release has a ton of features, but one specific for Microsoft Teams adding the capability to surface SPFx web parts inside a Microsoft Teams tab. As my talk will be about Microsoft Teams why not change the demo plans 72 hours before the talk and try something new?&lt;/p&gt;</description></item><item><title>Chrome SP Editor v4.1.4</title><link>https://thomygoelles.com/chrome-sp-editor-v4.1.4/</link><pubDate>Mon, 20 Aug 2018 10:51:12 +0000</pubDate><guid>https://thomygoelles.com/chrome-sp-editor-v4.1.4/</guid><description>&lt;p&gt;A couple of months ago I started playing with webhooks and SharePoint lists. After searching for the easiest way to configure a webhook I came across a feature in SP Editor by &lt;a href="https://twitter.com/tavikukko" target="_blank" rel="noopener"&gt;Tomi Tavela&lt;/a&gt;. By using the SP Editor you just need to open Chrome, navigate to your SharePoint site, press F12 and look for the Webhooks menu in the tool. Adding a webhook is done in two easy steps, selecting your list and provide the URL to your webhook, click save and that&amp;rsquo;s it. In my use case, I needed a small addition to that feature. A SharePoint webhook has an optional parameter called ClientState. This can be used to identify your webhook later on by just that variable. In the last week of July, I had the pleasure to be in Helsinki and meet with some local SharePoint guys including Tomi. If you already had the experience to feel that guys passion for his work and SharePoint development in general, it&amp;rsquo;s like a no-brainer to be motivated to give something back. It&amp;rsquo;s just a couple of lines of code added to the already awesome SP Editor and now starting with version 4.1.4 you are able to add a custom ClientState when adding a webhook to a SharePoint list. So, go check out the latest release of &lt;a href="https://chrome.google.com/webstore/detail/sp-editor/ecblfcmjnbbgaojblcpmjoamegpbodhd?hl=en" target="_blank" rel="noopener"&gt;SP Editor&lt;/a&gt; as it only will get better. &lt;/p&gt;</description></item></channel></rss>