jQuery 3.6.0 has been released! In jQuery 3.5.0, the major change was a security fix for the html prefilter. This release does not include a security fix, but does have some good bug fixes and improvements. We still have our eyes on a jQuery 4.0 release, but until then we will continue to support the 3.x branch and address important issues. 

Today, we’re announcing that Microsoft 365 apps and services will no longer support Internet Explorer 11 (IE 11) by this time next year.

• Beginning November 30, 2020, the Microsoft Teams web app will no longer support IE 11.
• Beginning August 17, 2021, the remaining Microsoft 365 apps and services will no longer support IE 11. 

We decided to use Qt for our next Geospatial Intelligence Desktop App, but the .NET Core performance was close to Qt and both easily outperformed the JavaFX prototype. So, we are going to use .NET Core for our Geospatial Intelligence Services backend. 

Today, we’re releasing .NET 5.0 Preview 6. It contains a small set of new features and performance improvements. The .NET 5.0 Preview 4 post covers what we are planning to deliver with .NET 5.0. Most of the features are now in the product, but some are not yet in their final state. We expect that the release will be feature-complete with Preview 8. 

• What is a SynchronizationContext?
• What is a TaskScheduler?
• How do SynchronizationContext and TaskScheduler relate to await?
• What does ConfigureAwait(false) do?
• Why would I want to use ConfigureAwait(false)?
• Why would I want to use ConfigureAwait(true)?
• When should I use ConfigureAwait(false)?
• ...

Intence is a new UX concept and a JavaScript library which reflects the scrolling state in a simple and intuitive manner. It highlights the scrollable area depending on the scrolling amount, thus efficiently explaining to a user what exactly can be scrolled, and is there much to scroll. Intence is suggested as a scrollbar replacament for a general designation of a scrollable area. The library is written in vanilla JavaScript and has no dependencies.  Demo

In this post, we are going to write about what we consider to be the best practices while developing the .NET Core Web API project. How we can make it better and how to make it more maintainable.

We are going to go through the following sections:

• Startup Class and the Service Configuration
• Project Organization
• Environment Based Settings
• Data Access Layer
• Controllers
• Actions
• Microsoft.AspNetCore.All Meta-Package
• Routing
• Logging
• CryptoHelper
• Content Negotiation
• Using JWT
• Conclusion  

Now that VNext builds are in Preview, you should be moving your build definitions over from the “old” XAML definitions to the new VNext definitions. Besides the fact that I suspect at some point that XAML builds will be deprecated, the VNext builds are just much better, in almost every respect.

Here I will try to give a few hints on how to create a good README file and what mistakes to avoid