Windows Subsystem for Linux 2 (WSL 2) is one of the most popular features for developers on Windows 10 and 11. It has recently been made available on Windows Server 2022. With this addition, you can now run Linux containers on WSL 2 on Windows Server 2022 for development and testing purposes. 

Here’s a look at a handful of the changes since our last alpha:

• Overhauled spacing utilities to use a numerical tiering (to avoid confusion with grid tiers).
• Continued refactoring efforts to replace markup-specific selectors with classes across several components (including pagination, lists, and more). Still more to do here with additional components.
• Reverted media queries and grid containers from rems to pixels as viewports are not affected by font-size. See #17403 for details. We’ve got a ton of grid work left, too. Feel free to follow along with#18471.
• Reverted .0625rem width borders to 1px for more consistent component borders that avoid zoom and font-size bugs across browsers.
• Renamed .img-responsive to .img-fluid to avoid future confusion on the various responsive image solutions out there.
• Replaced ZeroClipboard with clipboard.js for Flash-independent copy buttons.
• Inputs and buttons now share the same border variable to ensure components are always sized similarly.
• Updated all pseudo-element selectors to use the spec’s preferred double colon (e.g., ::before as opposed to :before).
• Cards now have outline variants and mixins to support extending base classes further.
• Utility classes for floats and text alignment now have responsive ranges. This means we’ve dropped the non-responsive classes to avoid duplication.
• Added support for jQuery 2.
• And hundreds more Sass improvements, bug fixes, documentation updates, and more. 

1. Debugging WPF Applications
2. Stepping Through Code
3. Working with Debug Windows
4. Debugger Visualizers and Trace Listeners
5. XAML Debugging
6. Analyzing the UI Performances
7. Analyzing the Application Performances 

ASP.NET Core 1.0 is the ground-up rewrite of ASP.NET, MVC and Web API, bringing a new paradigm in building web applications and APIs in .NET. With this rewrite brought new techniques in building SOLID applications, and updated some existing patterns and tools.
In this session, we'll take a lap around some of the major extension points of ASP.NET Core 1.0, walking through how these features can help us build cleaner, more maintainable systems. We'll cover web APIs, traditional MVC applications, controllers, views, filters, dependency injection, tag helpers and more. With a SOLID foundation, our ASP.NET Core applications will be dead simple to build and maintain.
 

• Use BindAttribute on the action method 
• Use [Editable] or [BindNever] on the model 
  
• Use two different models 
• Use a base class 
  
• Use ModelMetadataTypeAttribute 
  
• Explicit binding via TryUpdateModelAsync<> 
  

This was a very quick run down of some of the options available to you to prevent mass assignment. Which approach you take is up to you, though I would definitely suggest using one of the latter 2-model approaches. There are other options too, such as doing explicit binding via TryUpdateModelAsync<> but the options I've shown represent some of the most common approaches. Whatever you do, don't just blindly bind your view models if you have properties that should not be edited by a user, or you could be in for a nasty surprise.

And whatever you do, don't bind directly to your EntityFramework models. Pretty please. 

A new free extension for Visual Studio was released that enables developers to create cross-platform HTML5 applications exclusively using C# and XAML.