Today we're going to take a look at TypeScript, a compile-to-JavaScript language designed for developers who build large and complex apps. It inherits many programming concepts from languages such as C# and Java that add more discipline and order to the otherwise very relaxed and free-typed JavaScript

These are the customer-reported issues addressed in 15.7.2:

• With 15.7, users installing an extension on the command line with a nested extension may see an error installing. This has been addressed in the 15.7.2 servicing release.
• Anaconda fails to uninstall during upgrade and issues warning (Error 87).
• The SSDT 15.6.0 Installer configuration registry key could not be opened..
• Editor performance Issues when editing JavaScript.
• The Code Coverage functionality in Visual Studio 2017 ignores async methods.
• Missing atls.lib in arm/arm64 after update.
• Test Explorer no longer greys out the previously run unit tests.
• Version 15.7.1 debugs .aspx App in a new Chrome instance even if JavaScript debugging is disabled.
• 15.7 compiler fails with Folly.
• ASP project keeps running after closing the web page.
• Chrome Debugger not working and shows an error message, however, the debugger buttons stay active. .
• Rename Python from Rename on the Refactor menu no longer works.
• Visual Studio Installer doesn't work correctly in low disk space conditions.
• Debugger links to browser when previously not set.
• Problems with template argument deduction for class templates.
• C++ constexpr string_view == fails to compile.
• A regression in Type Providers which use native resources (e.g., FSharp.Data.TypeProviders) has been fixed.
• You can now add files to F# ASP.NET Core projects from the UI.
• Listening to Microsoft-Extensions-Logging causes VS diagnostic events window to disconnect with an error message has been fixed in Service Fabric Tools. 

Come to hear the future of Visual Studio. This session will illustrate how Visual Studio is evolving demo by demo. We’ll show you the latest capabilities to enable any developer to build any apps. We’ll provide a preview of the streamlined acquisition experience for the next release of Visual Studio. You will see the cutting edge features we are working on to bring your productivity to the next level. We’ll even provide a back stage peek into how we’re using your feedback to continuously improve Visual Studio.
 

Chrome has been testing an emoji keyboard for a long time

Finally, Standard Edition customers have a replacement for Database Mirroring, which has been deprecated.

These are the customer-reported issues addressed in 15.9.5:

• VSX1000: No enough information has been provided to MSBuild in order to establish a connection to a Remote Server.
• Visual C++ 2017 Redistributable for ARM64 is not available via visualstudio.com.
• VC Runtime Redistributable Update for VS 15.9 deletes Registry Key. This fix may have an increased chance of requiring a reboot of the machine in order to install an updated VC++ Redistributable package.
• Incorrect codegen in managed c++ with List to List assignment.
• Can't connect to mac build host after Visual Studio 15.9.4 update.
• Resource directories missed in incremental builds with AndroidAarLibrary items.
• Lots of external assembly references - JNI ERROR (app bug): local reference table overflow (max=512).
• The Unity Editor has been updated to 2018.3. For more information, please visit the Unity website.
• SSDT: We enabled SQL projects to build schemas that have non-clustered columnstore indexes on an indexed views.
• SSDT: We fixed a significant performance issue in the schema compare tool when generating a script.
• SSDT: We fixed the schema drift detection logic in the schema compare tool which forced a new comparison to reenable scripting and publishing actions.

Security Advisory Notices

• A remote code execution vulnerability exists in Visual Studio when the C++ compiler improperly handles specific combinations of C++ constructs. 

Firstly, it’s not a done deal. An offer has been made, and Opera’s board has recommended that shareholders accept it. But shareholders need to vote and governments need to be consulted. 

GitHub Issues

The GitHub Issues integration allows you to search and reference your issues from the commit message box in VS, in response to this suggestion ticket. You can reference an issue or a pull request by typing # or clicking on the # button in the lower right side of the commit message text box. If you weren't already authenticated to access related issues, you will now be prompted to sign in to take advantage of this feature.

Line Unstaging

To continue improving our line-staging (aka interactive staging) feature, we've added unstage. You can now use the tool tip option to unstage changes, line by line, as requested here Unstage individual lines and hunks in a file - 4 votes

Arm64

We continue to build native support for Arm64 on Windows 11 for the most popular developer scenarios. We now support the .NET Multi-platform App UI (MAUI) workload on Arm64 Visual Studio.

C++

• Available as a preview feature, you can now view Unreal Engine logs without leaving VS. To see the logs from the Unreal Engine Editor, click View > Other Windows > UE Log. To filter your logs, click on the "Categories" or "Verbosity" dropdowns. Since this is an experimental feature, feedback is greatly appreciated.
• You can now import STM32CubeIDE projects for embedded development within Visual Studio with File > Open > Import STM32CubeIDE project. This generates a CMake project with device flashing and debugging settings for STLink. You must have the STM32CubeIDE installed with the board support package for your device. More details available here.
• You can use the new CMake Debugger to debug your CMake scripts at build time. You can set breakpoints based on filenames, line numbers, and when CMake errors are triggered. Additionally, you can view call stacks of filenames and watch defined variables. Currently, this only works with bundled CMake, and projects targeting WSL or remote machines are not supported yet. We are actively working to add more support to the CMake debugger, and feedback is greatly appreciated. 

In any good programming reference, you will read that a developer has to document his code, not only for him/herself, but also for the person who, ten years later will be asked to maintain it. This would, of course, be made easier thanks to a good documentation of existing code. 

A foreign worker has a sponsoring firm that handles the lengthy green-card process. If the developer leaves the firm a year into the process, they need to restart the green-card process from beginning