Angular 1.3 might be the best Angular yet, but there's still lots of high impact work to be done on the 1.x branch. We still have Material Design, our new router, and improved internationalization of Angular apps still to come ... 

The Angular 1.x project needs someone to be fully committed to keeping v1 moving forward, and supporting the Angular ecosystem that has grown around it.

That's why I'm delighted that Pete Bacon Darwin has agreed to take over the leadership role for Angular v1.  

But Pete can't do this alone. He needs Brian, Caitlin, and Chirayu to help make v1 even more awesome. Jeff will help out with google3 sync and releases, and familiar faces like Matias Niemela and Pawel Kozlowski (who co-wrote one of the first books on Angular with Pete) will be ongoing contributors. We're also looking forward to meeting new faces. Over time, some of these folks will shift their focus towards Angular 2, but for the immediate future, what's most important is that Angular 1.x is and continues to be well taken care of.  

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 

VSTest is a very extensible unit test execution framework.  The base engine, discovers tests and runs them.  It can parallelize across cores, provides process isolation and can integrate with Visual Studio.  It has extensibility for different test frameworks, code coverage, test impact analysis, data collection, test result reporting and much more. 

The May release of Visual Studio Code is out, including better IntelliSense, faster step-by-step debugging, and more. 

DNX, a Dot Net eXecution environment, contains all of the code that is required to bootstrap and run an application.

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. 

Partial views in ASP.NET MVC allow you to reuse and customise components to act like user controls. They consist of both code and markup. They are an idea that is easy to grasp but they have great potential for the more adventurous developer who is prepared to experiment. Dino Esposito explains