Software Update: Microsoft Visual Studio 2019 16.10.4

Microsoft has released version 16.10.4 of Visual Studio 2019. This popular programming development environment has useful options to make programming easier in Visual C++, Visual Basic, C#, F#, Python and R, among others. The complete list of the changes in the 2019 edition can be found in the accompanying release notes. In version 16.10.4, Microsoft has made the following improvements:

Top Issues Fixed in this Release

• Remove use of disallowed registers in memset.
• Fixed a codegen bug involving complicated nested expressions involving the bitwise-not operator.
• Fixed shader debugging for VS Graphics Analyzer
• Fixed an IntelliSense crash that occurred when processing static data members in in-class template specializations.
• X64 VC Redist no longer removes runtime files when run with /installer /passive switches.
• Corrected an issue where the include search order may be incorrect when prepended to “Include Directories”.
• We have fixed performance problem and false positives caused by one of the checker extensions that finds bugs in misuse of VARIANTs.
• We have fixed performance problem caused by one of the checker extensions that finds bugs in misuse of enum values ​​as index.
• Introduces Live Share language services fix that restores major code editing features for collaboration session participants (code completion, syntax highlighting, errors, etc.)
• Concurrency analyzer should no longer produce false warnings C26110 (failure to acquire lock) with auto-lock patterns.
• C# and Visual Basic compilers fixed a crashed involving InternalsVisibleTo clashing with other assembly level attributes.
• We have fixed an issue experienced by customers packaging their projects with Windows Application Packaging Projects, such as WPF NetCore apps and Project Reunion apps:
  Error Assets file ‘…objwappublishwin10-x86project.assets.json’ not found. Run a NuGet package restore to generate this file. App4 (Package) C:Program Filesdotnetsdk5.0.302SdksMicrosoft.NET.SdktargetsMicrosoft.PackageDependencyResolution.targets 242
  This problem was caused by the Packaging Project looking for the project.assets.json file in the wrong directory, win10-$(configuration), when it should be looking in win-$(configuration).