About six months ago, I built a small API application designed specifically for Azure. It leveraged several Azure-native features, including synchronization mechanisms and Azure App Registration for sending requests to SharePoint. The application was built using .NET 8 and deployed to a development environment.

When you want to send to your colleague a text with C# code or any other language, you can make the code look just like in an IDE - colored and highlighted.

If you type three backticks ``` at the beginning of a line in Microsoft Teams and press Enter, you can write properly formatted code in the chat. Almost like in MarkDown.

It opens a code block where:

• The formatting is preserved
• The text appears in a monospace font
• Your code is much easier to read

It's very useful when while technical topics with your team.

Did you know that in Visual Studio you can execute just a selected piece of code without running the whole application? There’s a handy (and surprisingly little-known) shortcut for this:
Select the code and press Ctrl + E and then again Ctrl + E.

After importing a WSL distribution and copying files from one WSL instance to another, I ended up with thousands of files with :Zone.Identifier at the end of their names. Zone.Identifier is a Windows security metadata stream that marks files downloaded from the Internet.

Support for SharePoint Server 2019 officially ends on Tuesday, July 14, 2026. That’s less than six months away — and for many organizations, this date is approaching faster than expected. SharePoint 2019 has been a stable and reliable on-premises platform for years, but the end of mainstream support is an important milestone that should not be ignored.

When developing applications, there are times when you need to temporarily change the behavior of a working method — for example, to investigate a bug, check something quickly, or work around an issue for the moment.

In this post I will tell you how to upgrade the version of the SPFX framework of the existed solution. Here is the information only about SharePoint online, because for SharePoint 2019 On-premises you can use only NodeJs 10 and spfx 1.4.0.

I often use Linux, even though Windows is my main operating system. For me, Windows works best for everyday tasks, while Linux is ideal for servers and development environments. Some people agree with this approach; others prefer a single OS for everything.

This post is about how to crate a list item in SharePoint list in backend process. It can be API, background service, azure function, mobile or desktop app. So, it can be anything you want, but in .Net. And we will use SharePoint Rest API, that is wrapped by CSOM (Microsoft.SharePointOnline.CSOM).

Today I lost way too much time trying to understand why I couldn’t see data in a PostgreSQL database running inside a Docker container. I was connected via DBeaver, everything looked fine:

• connection successful
• schemas visible
• but no tables