Top Issues Fixed in Visual Studio 2019 version 16.4.1

• Fixed "the write operation failed. you must first acquire write access from dataschemamodelcontroller" error trying to publish a database
• Fix ExecutionEngineException exceptions when using SignalR on iOS devices in some configurations
• Runtime Fix "CEE_RET: value type stack" crash when interpreter was enabled with some libraries
• TypeScript 3.7.3 is now included by default, which contains several fixes for issues that effect the JavaScript and TypeScript editing experience.
• May allow mitigation of a Per-Monitor awareness related crash in Visual Studio

Security Advisory Notice

CVE-2019-1349 Git for Visual Studio Remote Excecution Vulnerability due to too lax restrictions on submodule names

CVE-2019-1350 Git for Visual Studio Remote Excecution Vulnerability due to incorrect quoting of command-line arguments

CVE-2019-1351 Git for Visual Studio Arbitrary File Overwrite Vulnerability due to usage of non-letter drive names during clone

CVE-2019-1352 Git for Visual Studio Remote Excecution Vulnerability due to unawareness of NTFS Alternate Data Streams

CVE-2019-1354 Git for Visual Studio Arbitrary File Overwrite Vulnerability due to not refusing to write out tracked files containing backslashes

CVE-2019-1387 Git for Visual Studio Remote Execution Vulnerability due to too lax validation of submodule names in recursive clones

CVE-2019-1486 Live Share extension URL redirection vulnerability

In this article, 10 best practices in async-await code in C# is discussed that you should keep in mind when  developing asynchronous code in .NET 

There are two things you should keep in mind:
 1. Don't wrap asynchronous tasks in another call to Task.Run().
 2. Don't use asynchronous wrappers over synchronous calls.

On over-engineering; finding the right balance

A big debate among developers is whether to write code for today’s problem or to build a general-purpose solution for future needs. Both approaches have their pros and cons. Specific-purpose code can quickly become messy. But overly general code can add unnecessary complexity. This post, obviously opinionated, argues for a middle ground. That’s the sweet spot, as always.