Top Issues Fixed in Visual Studio 2019 RC.2

• Find in files "Locating next match" UI is annoying.
• Find files keeps defaulting to current document.
• Quick references freezes VS 2019 RC.
• PackageId:MsSqlCmdLnUtils;PackageAction:Install;ReturnCode:1603;.
• Error List does not show errors because it is scoped to "Current Document".
• Cannot use conditional breakpoint on PropertyInfo.Name value.
• Visual Studio crashes when parsing macros at the end of a file.
• Search in Visual Studio 2019 is very slow.
• Visual Studio hangs when starting debugging.
• vdproj not supported in Visual Studio 2019 RC.
• Visual Studio installer welcome image contains offensive element for Chinese.
• VSIX Extension pre-req has been removed in Visual Studio 2019 RC breaking extension compatibility.
• Create Project from Start Screen Ignores Selected Project Folder.
• cpp properties is dialog does not show up when using Project menu item or select "Manage configuration" drop down menu.
• Visual Studio 2019 Build Tools - developer prompt title says "Developer Command Prompt for Visual Studio 2017".
• German tranlation regarding the Feedback Tool: Help > Send Feedback > Report a Problem.
• 自动完成功能，如果双击候选项，会丢失输入焦点，需要单机编辑器才能继续输入-AutoComplete function, if you double-click the candidate, will lose the input focus, need a stand-alone editor to continue to enter.
• Context menus are sometimes placed on the wrong monitor in a multiple monitor configuration.
• Visual Studio 2019 conflict with QQ Pinyin.
• Cannot drag maximized Visual Studio window.
• Fixed slow reload of multiple C# and Visual Basic projects.
• When IntelliSense is present, when a user types Shift + Enter, the active selection will be completed and a new line inserted.
• Fixed a PMA issue where editor tooltips and light bulb doesn't render properly.
• Notifications about crashes caused by extensions now show up again.
• Notifications about performance of Visual Studio have been secured against tampering.
• Fixed an issue with toolbar rendering when dragged across displays.
• Fixed an issue with Tools Options rendering when running with per-monitor awareness enabled.
• Various DpiHelper classes has been deprecated (extensibility).
• Fixed splash screen scaling to better match the primary monitor scale factor.
• Fixed an issue in settings import where warnings/errors were not always reported correctly.
• Fixed an issue where Tools Options reported software rendering regardless of rendering tier.
• Fixed an issue where the name of the open folder was not displayed in the title bar region.
• Fixed an issue with find in files positioning when per-monitor awareness is enabled.
• Fixed an issue with dock adorner rendering when per-monitor awareness is enabled. 

Here are some of the reasons why nullable reference types are less than ideal:

• Invoking a member on a null value will issue a System.NullReferenceException exception, and every invocation that results in a System.NullReferenceException in production code is a bug. Unfortunately, however, with nullable reference types we “fall in” to doing the wrong thing rather than the right thing. The “fall in” action is to invoke a reference type without checking for null.
• There’s an inconsistency between reference types and value types (following the introduction of Nullable<T>) in that value types are nullable when decorated with  “?” (for example, int? number); otherwise, they default to non-nullable. In contrast, reference types are nullable by default. This is “normal” to those of us who have been programming in C# for a long time, but if we could do it all over, we’d want the default for reference types to be non-nullable and the addition of a “?” to be an explicit way to allow nulls.
• It’s not possible to run static flow analysis to check all paths regarding whether a value will be null before dereferencing it, or not. Consider, for example, if there were unmanaged code invocations, multi-threading, or null assignment/­replacement based on runtime conditions. (Not to mention whether analysis would include checking of all library APIs that are invoked.)
• There’s no reasonable syntax to indicate that a reference type value of null is invalid for a particular declaration.
• There’s no way to decorate parameters to not allow null. 

The PDF File Writer C# class library PdfFileWriter allows you to create PDF files directly from your .net application.
Most TrueType fonts such as Arial supports character values greater than 255. The PDF File Library allows you to perform a substitution. You can use any Unicode character and map it into the available one byte range.

By default the .NET Framework/Mono variants are still used, but you can opt into having the .NET 6.0 builds by setting the following in your VS Code settings

{
    "omnisharp.useModernNet": true
}

Bit works with Git and NPM to easily share and sync code between projects

Simple i18n support for your Angular apps 

 Easy ways to create a translation mechanism for your Angular and Ionic applications that does not rely on third-party libraries.

In this article, I am going to show a quick and easy way to provide a translation (aka i18n) support for your Angular and Ionic applications. 

Visual Studio Community 2017 RC is a free, fully featured, and extensible IDE for individual developers, open source projects, education and academic research. You can create applications for Android, iOS, Windows and the web. Integrated Azure tools make it e 

Integrated Terminal improvements - Find support, select/copy multiple pages.
Command Palette MRU list - Quickly find and run your recently used commands.
New Tasks menu - Top-level Tasks menu for running builds and configuring the task runner.
Automatic indentation - Auto indent while typing, moving, and pasting source code.
Emmet abbreviation enhancements - Add Emmet to any language. Multi-cursor support.
New Diff review pane - Navigate Diff editor changes quickly with F7, displayed in patch format.
Angular debugging recipe - Debug your Angular client in VS Code.
Better screen reader support - Aria properties to better present list and drop-down items.
Preview: 64 bit Windows build - Try out the Windows 64 bit version (Insiders build).
Preview: Multi-root workspaces - Open multiple projects in the same editor (Insiders build).