webpack is arguably the most popular bundler right now and this is the first major release in over two years. We get big improvements to caching (and therefore performance), reduced bundle sizes with better tree shaking, and a variety of breaking changes to prepare for the future (automatic Node polyfills are gone, for one). 

This guest blog post is the first of a 3-part series written by Windows MVP Jani Nevalainen. 

Issues fixed in Visual Studio 2019 version 16.0.4

• Attach to iis prompt to attach multiple times.
• WPF applications broken after FW 4.8 update.
• installing typescript 3.3 disables version 2.2 compilation.
• Unable to attach debugger when attaching multiple startup projects on Visual Studio 2019.
• Known issue: Application tab of VB project property pages is broken when isntalling the .NET Framework 4.8 Developer Pack.
• Visual Studio extensions may fail to install attempting to overwrite core NuGet files.
• microsoft.diagnosticshub.dotnetobjectalloc.vsix missing from offline installer.

Security Advisory Notices

CVE-2019-0727 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly performs certain file operations. An attacker who successfully exploited this vulnerability could delete files in arbitrary locations. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by securing locations the Diagnostics Hub Standard Collector performs file operations in. 

We’re excited to announce general availability of F# 4.7 in conjunction with the .NET Core 3.0 release! In this post, I’ll show you how to get started, explain everything in F# 4.7 and give you a sneak peek at what we’re doing for the next version of F#. 

Soon the next major version of the framework will come out, which breaks backward compatibility. Apparently, even developers of the framework realized that there is something wrong and decided to rewrite the framework almost from scratch. They don’t add new functionality, breaking backward compatibility, they rewrite almost everything. 

Team Explorer support for TLSv1.2

• We have updated the Git and the Git Credential Manager components that ship in Visual Studio.
• The optional Git for Windows component has also been updated.
• This update allows Git to connect to services that have deprecated support for TLSv1 and TLSv1.1 in favor of TLSv1.2.

Issues Fixed in this Release

These are the customer-reported issues addressed in this release:

• Projects targeting .NET Core 2.1 or newer are not supported by Visual Studio 2017 version 15.5.
• Fixed issue where installation of the SDK for .NET Core 2.1 or newer would cause the option to create ASP.NET Core 2.0 Web applications to disappear. 

As of r202125, JavaScriptCore supports all of the new features in the ECMAScript 6 (ES6) language specification. All of the new ES6 features are available in the latest WebKit Nightly and Safari Technology Preview.  

This post provides a simple IValueConverter implementation that makes use of the framework type converters in order to convert between a large range of source / target types. This converter can be used both within bindings and in code-behind to give more concise property setters.