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

At my previous job I was happy to work with SharePoint on-premises. More than 10 years with SP 2007, 2010 and finally 2019. Almost 3 years ago I thought I won't cooperate with it. In May 2026 the support of SharePoint server ends. But as it turned out many companies still use SP on-prem and don't want to migrate.

In this example here will be the mixed scenario. The parent component has states, and the child component. It's the mixed implementation. Of course, usually you make everything in the same style, but there are situations, when you need the mixed implementation.

The app that I am developing now connects to Azure services and DefaultCredential were used for that. In Azure the authentication between services works with managed identities and I am satisfied with them, but while the development I've got an error "Azure.RequestFailedException: Server failed to authenticate the request", so I really didn't know what to do. Yesterday it worked, today not.