Top Issues Fixed in Visual Studio 2019 RC.1

• Visual Studio 2019 Preview 4 crash if closing undocked Window.
• Intellisense error: C++11 static constexpr member initialization causes "member may not be initialized".
• Start Page "Remove From List" stops working.
• $(VCIDEInstallDir) is an invalid path. Missing backslash in Microsoft.Cpp.Common.props.
• Visual Studio 2019 Preview 2.0+ crashes when opening soultion filter.
• Manage Extensions toolbar throws exception.
• Fixed rendering of the Import and Export Settings Wizard when running per-monitor aware
• Fixed sizing of the New Project Dialog when running per-monitor aware
• Made a set of visual refinements to the start window 

In this article I’ll teach you how to use CSS Grid to create a super cool image grid which varies the amount of columns with the width of the screen. 

For .NET and cloud developers, we’ve focused on improving the inner-loop dev experience. New .http/.rest files make it easier to test and iterate on your APIs directly in Visual Studio, while improved Dev Tunnels help streamline the configuration and management of your webhooks. We’ve also made it easier than ever to deploy your ASP.NET apps to containers.

Game developers can now view properties from base classes modified in an Unreal Blueprint asset without leaving the IDE. Visual Studio has improved the cross-platform development experience with a new remote file explorer, Linux Console output to the Integrated Terminal window, dev container improvements, and more.

Beyond individuals, Visual Studio also has new features to better support dev teams at scale, with exportable configuration files and a persistent update toggle helping ensure everyone on your team is working from the latest version of the tool.

This blog covers several of the top new features in Visual Studio 17.5—to see some in action, watch the Visual Studio 17.5 release video. As always lot of these features come straight from your feedback and suggestions. Your feedback is critical to help us make Visual Studio the best tool it can be! 

As stated in this article, Windows 10, version 1909 is a scoped set of features for select performance improvements, enterprise features and quality enhancements. Developers should be aware of this release, but no action is necessary at this time. 

This is a list of some of the available Entity Framework Core extensions out there that expand the functionality of the Entity Framework Core runtime. Only libraries that extend DbContext or similar are included, and they must be published on NuGet.org.

Before we dive into the technical details, let’s start with a quick history lesson, courtesy of Don Syme who worked on adding generics to .NET and then went on to design and implement F#, which is a pretty impressive set of achievements!!

Background and History

• 1999 Initial research, design and planning
  • .NET/C# Generics History: Some Photos From Feb 1999
• 1999 First ‘white paper’ published
  • More C#/.NET Generics Research Project History – The MSR white paper
  • MSR White Paper: Proposed Extensions to COM+ VOS (Draft) (pdf)
• 2001 C# Language Design Specification created
  • Some History: 2001 “GC#” (Generic C#) research project draft
  • MSR - .NET Generics Research Project - Generic C# Specification (pdf)
• 2001 Research paper published
  • Design and Implementation of Generics for the .NET CLR (pdf)
• 2004 Work completed and all bugs fixed
  • Some more .NET/C# Generics Research Project History 

The .NET Framework 4.7 includes improvements in several areas:

1. High DPI support for Windows Forms applications on Windows 10
   
2. Touch support for WPF applications on Windows 10
   
3. Enhanced cryptography support
   
4. Performance and reliability improvements 
   

Any experienced .NET developer knows that even though .NET applications have a garbage collector, memory leaks occur all the time. It’s not that the garbage collector has bugs, it’s just that there are ways we can (easily) cause memory leaks in a managed language.

Memory leaks are sneakily bad creatures. It’s easy to ignore them for a very long time, while they slowly destroy the application. With memory leaks, your memory consumption grows, creating GC pressure and performance problems. Finally, the program will just crash on an out-of-memory exception.

In this article, we will go over the most common reasons for memory leaks in .NET programs. All examples are in C#, but they are relevant to other languages.  

Here’s a quick rundown of some of the changes:

• Added validation styles for file inputs
• Improved printing of dark tables
• Suppressed that text-hide deprecation notice by default
• Fixed an issue where Collapse wasn’t working in Internet Explorer
• Cleaned up some JS globals and improve coverage
• Bumped dependencies, namely Jekyll
• Fixed docs issue with incorrect name for our monospace font utility