Summary of Notable New Features in 15.9

• You can now import and export an installation configuration file that specifies which workloads and components should be installed with an instance of Visual Studio.
• We have improved the debugging experience for NuGet packages using the new symbol package format (.snupkg).
• Step back in debugger is now available in C++ for Enterprise customers.
• C++ IntelliSense now responds to changes in the remote environment for both CMake and MSBuild projects targeting Linux.
• We have made updates to UWP Desktop Bridge framework packages and added support for ARM64 C++ Native Desktop scenarios.
• We added support for the range-v3 library with the MSVC 15.9 compiler.
• We fixed several bugs in the F# compiler and F# tools.
• Language service support for new TypeScript features for semantic file renaming and project references.
• Improved Node.js development by updating Vue.js templates and adding support for unit testing using the Jest framework.
• We added SharePoint 2019 project templates, so you can migrate existing SharePoint 2013 and 2016 projects to SharePoint 2019.
• Visual Studio Tools for Xamarin now supports Xcode 10.
• We made improvements to the Xamarin.Android build performance.
• We have added and improved features for Universal Windows Platform developers, including ARM64 support, the latest preview SDK, better debugging of Desktop Bridge applications, and XAML Designer improvements.
• Substantial improvements were made to the experience of using authenticated package feeds.
• There is now support for lock file to enable repeatable restore for PackageReference based projects.
• We have added support for the new license format for NuGet packages.
• We have introduced NuGet client policies in Visual Studio which enables you to lock down environments such that only trusted packages can be installed.
• We made the use of .NET Core within Visual Studio more predictable.

Top Issues Fixed in 15.9

• No way to change "Find All References" background color.
• "Visual C++ Resource Editor Package" load failed.
• VS2017 v15.8 Build does not start if XAML files are not manually saved first.
• Installation failed - manifest signature verification failed.
• Update 15.8.6 breaks Installer Projects.
• Scrolling up with the arrow key causes Visual Studio to page up.
• After updating to 15.8.1, data tip does not show when debugging.
• System.InvalidProgramException: Common Language Runtime detected an invalid program..
• Solution Explorer does not remain pinned after closing Visual Studio.
• Navigation bar in editor has trouble handling long method names. 

 Uninstall-Package Microsoft.AspNet.SignalR -RemoveDependencies

 Install-Package Microsoft.AspNet.SignalR

 <script src="Scripts/jquery.signalR-2.0.0.min.js"></script>

 protected void Application_Start(object sender, EventArgs e)
{
   //RouteTable.Routes.MapHubs();
}

using Microsoft.Owin;
using Owin;

[assembly: OwinStartup(typeof(SignalRChat.Startup))]
namespace SignalRChat
{   
    public class Startup
    {
        public void Configuration(IAppBuilder app)
        {
            app.MapSignalR();
        }
    }
}

Angular 16 CRUD with .NET 7 Web API using Entity Framework Core - Full Course

📑 Contents:
00:00:00 Video Introduction
00:00:40 Angular and ASP.NET Core Udemy Course Demo
00:03:07 Prerequisites
00:03:37 Setting Up Development Environment
00:15:37 Create ASP.NET Core Web API
00:20:07 Understanding Files and Folder Structure
00:25:37 Understanding REST and HTTP Verbs
00:30:10 Create .NET 6 Web API
00:32:41 Our Project and Domain Models
00:41:16 Installing Nuget Packages For Entity Framework Core
00:43:06 DbContext
00:59:26 Running EF Core Migrations
01:03:26 Create Controllers and Actions
01:23:46 Repository Pattern
01:36:46 Create New Angular Application using Angular CLI
01:50:09 Angular Components
02:13:29 CRUD in Angular and ASP.NET Core Web APIs
02:17:21 Angular Forms
02:26:59 Angular Services
02:38:09 CORS
02:42:09 Unsubscribing
 

A library that provides a simple way to create lambda expressions to filter lists and database queries. 

var filter = new Filter<Person>();
filter.By("Id", Operation.Between, 2, 4,  Connector.And);
filter.By("Contacts[Value]", Operation.EndsWith, "@email.com", default(string), Connector.And);
filter.By("Birth.Country", Operation.IsNotNull, default(string), default(string),  Connector.Or);
filter.By("Name", Operation.Contains, " John");
var people = People.Where(filter);

//or like this...

var filter = new Filter<Person>();
filter.By("Id", Operation.Between, 2, 4)
      .And.By("Birth.Country", Operation.IsNotNull)
      .And.By("Contacts[Value]", Operation.EndsWith, "@email.com")
      .Or.By("Name", Operation.Contains, " John ");
var people = People.Where(filter);

So that would generate an expression like this: 

People.Where(p => (p.Id >= 2 && p.Id <= 4)
             && (p.Birth != null && p.Birth.Country != null)
             && (p.Contacts != null && p.Contacts.Any(c => c.Value.Trim().ToLower().EndsWith("@email.com")))
             || (p.Name != null  && p.Name.Trim().ToLower().Contains("john")));

LambdaExpressionBuilder Nuget Package 

Issues fixed in Visual Studio 2019 version 16.0.4

• Attach to iis prompt to attach multiple times.
• WPF applications broken after FW 4.8 update.
• installing typescript 3.3 disables version 2.2 compilation.
• Unable to attach debugger when attaching multiple startup projects on Visual Studio 2019.
• Known issue: Application tab of VB project property pages is broken when isntalling the .NET Framework 4.8 Developer Pack.
• Visual Studio extensions may fail to install attempting to overwrite core NuGet files.
• microsoft.diagnosticshub.dotnetobjectalloc.vsix missing from offline installer.

Security Advisory Notices

CVE-2019-0727 Diagnostics Hub Standard Collector Service Elevation of Privilege Vulnerability

An elevation of privilege vulnerability exists when the Diagnostics Hub Standard Collector Service improperly performs certain file operations. An attacker who successfully exploited this vulnerability could delete files in arbitrary locations. To exploit this vulnerability, an attacker would require unprivileged access to a vulnerable system. The security update addresses the vulnerability by securing locations the Diagnostics Hub Standard Collector performs file operations in. 

ExtCore allows you to decouple your application into the modules (or extensions) and reuse that modules in other applications in various combinations. Each ExtCore extension may consist of one or more projects and each project may include everything you want (as any other ASP.NET Core project). Controllers, view components, views (added as resources and/or precompiled), static content (added as resources) will be resolved automatically. These projects (extension pieces) may be added to the application directly as dependencies in project.json of your main application project (as source code or NuGet packages), or by copying compiled DLL-files to the Extensions folder. ExtCore supports both of these approaches out of the box and at the same time. 

JetBrains.Annotations

using JetBrains.Annotations;  


[assembly: AspMvcViewLocationFormat("~/Features/{1}/{0}.cshtml")]
[assembly: AspMvcViewLocationFormat("~/Features/Shared/{0}.cshtml")]
[assembly: AspMvcPartialViewLocationFormat("~/Features/{1}/{0}.cshtml")]
[assembly: AspMvcPartialViewLocationFormat("~/Features/Shared/{0}.cshtml")]

[assembly: AspMvcAreaViewLocationFormat("~/Areas/{2}/Features/{1}/{0}.cshtml")]
[assembly: AspMvcAreaViewLocationFormat("~/Areas/{2}/Features/Shared/{0}.cshtml")]
[assembly: AspMvcAreaViewLocationFormat("~/Features/Shared/{0}.cshtml")]
[assembly: AspMvcAreaPartialViewLocationFormat("~/Areas/{2}/Features/{1}/{0}.cshtml")]
[assembly: AspMvcAreaPartialViewLocationFormat("~/Areas/{2}/Features/Shared/{0}.cshtml")]
[assembly: AspMvcAreaPartialViewLocationFormat("~/Features/Shared/{0}.cshtml")]