.NET Framework is still an important platform for critical applications out there, but from time to time, its support policies from Microsoft change in favor of newer platforms. If you still own applications running on .NET Framework, it is recommended that you follow such policy changes and plan your migration accordingly.
I blogged about
Microsoft.Web.Administration a long while ago, but intentionally I left a small topic aside. However, it remains a misery sometimes painful to developers, so here comes a dedicated post.
If today you still run an application on Mono, I suggest you assert again whether that decision is sustainable. A look back on the Mono history can easily tell that it can be a risky platform to use in 2021 and beyond.
I wrote a language server prototype for reStructuredText in 2017 (let’s call it rst-antlr), which helped create some basic functionality in the reStructuredText VSCode extension. But in the next few years I didn’t have too much time to extend it further.
That approach has several limitations,
- The language parser in C# is rather hard to improve, as the original language specification and implementation is Python based.
- Too many gaps are there to fill.
It was a few weeks ago that I noticed MongoDB guys launched a language server for their internal documentation system named Snooty, and that language server contains reStructuredText support, which is based on docutils. And no doubt, time to integrate Snooty with reStructuredText VSCode extension.
Again this post comes from a Stack Overflow thread.
.NET 5 was released a few weeks ago, and 2020 is coming to an end. So now let’s talk about the stories around .NET Framework Reference Source, which almost always stays in the shadows.