With .NET 5, direct support of WinRT has been removed from the C# language and CLR, including most of the functionality previously provided in System.Runtime.InteropServices. In some cases, C#/WinRT provides equivalent functionality. In other cases, functionality may no longer be supported. This article provides a migration guide for interop scenarios in C#/WinRT. 

I've been doing some work the last couple of weeks with Angular2. I really like it. Not just because it uses typescript, but also because it feels really natural and straightforward while working with it. No more string based dependency injection, or strange digest cycle stuff, it just seems to work. This last week I've migrated our beta-13 Angular app to the latest rc-1, and used that to keep track of the fun and easy stuff Angular 2 provides. Note though, that the application we're developing is really that complex, so I can only assume we'll run into more complex Angular2 features in the near future. For now, though, let me share some general tips and tricks we've encountered thus far (in no particular order). Oh, all examples are in typescript, since after using that, I really don't want to go back to plain old javascript (POJS?). 

Here’s what’s new in this release:

• Azure Active Directory authentication with Microsoft.Identity.Web
• CSS isolation for Blazor components
• Lazy loading in Blazor WebAssembly
• Updated Blazor WebAssembly globalization support
• New InputRadio Blazor component
• Set UI focus in Blazor apps
• Influencing the HTML head in Blazor apps
• IAsyncDisposable for Blazor components
• Control Blazor component instantiation
• Protected browser storage
• Model binding and validation with C# 9 record types
• Improvements to DynamicRouteValueTransformer 
• Auto refresh with dotnet watch 
• Console Logger Formatter
• JSON Console Logger 

 npm update -g

 ng new MaterialAngularClient --routing

cd MaterialAngularClient
ng serve -o

 ng add @angular/material

npm install --save @angular/material @angular/cdk
npm install --save @angular/animations
npm install --save hammerjs

 import "hammerjs";

import { BrowserAnimationsModule } from "@angular/platform-browser/animations";

@NgModule({
  imports: [
    BrowserModule,
    BrowserAnimationsModule,
    AppRoutingModule
  ]
})
export class AppModule { }

import { CommonModule } from "@angular/common";
import { NgModule, Optional, SkipSelf } from "@angular/core";
import { RouterModule } from "@angular/router";


@NgModule({
  imports: [CommonModule, RouterModule],
  exports: [
    // components that are used in app.component.ts will be listed here.
  ],
  declarations: [
    // components that are used in app.component.ts will be listed here.
  ],
  providers: [
    /* ``No`` global singleton services of the whole app should be listed here anymore!
       Since they'll be already provided in AppModule using the `tree-shakable providers` of Angular 6.x+ (providedIn: 'root').
       This new feature allows cleaning up the providers section from the CoreModule.
       But if you want to provide something with an InjectionToken other that its class, you still have to use this section.
    */
  ]
})
export class CoreModule {
  constructor(@Optional() @SkipSelf() core: CoreModule) {
    if (core) {
      throw new Error("CoreModule should be imported ONLY in AppModule.");
    }
  }
}

import { CommonModule } from "@angular/common";
import { HttpClientModule } from "@angular/common/http";
import { ModuleWithProviders, NgModule } from "@angular/core";
import { FormsModule } from "@angular/forms";

@NgModule({
  imports: [
    CommonModule,
    FormsModule,
    HttpClientModule
  ],
  entryComponents: [
    // All components about to be loaded "dynamically" need to be declared in the entryComponents section.
  ],
  declarations: [
    // common and shared components/directives/pipes between more than one module and components will be listed here.
  ],
  exports: [
    // common and shared components/directives/pipes between more than one module and components will be listed here.
    CommonModule,
    FormsModule,
    HttpClientModule,
  ]
  /* No providers here! Since they’ll be already provided in AppModule. */
})
export class SharedModule {
  static forRoot(): ModuleWithProviders {
    // Forcing the whole app to use the returned providers from the AppModule only.
    return {
      ngModule: SharedModule,
      providers: [ /* All of your services here. It will hold the services needed by `itself`. */]
    };
  }
}

import { CoreModule } from "./core/core.module";
import { SharedModule } from "./shared/shared.module";

@NgModule({
  imports: [
    BrowserModule,
    BrowserAnimationsModule,
    CoreModule,
    SharedModule.forRoot(),
    AppRoutingModule
  ]
})
export class AppModule { }

import { CdkTableModule } from "@angular/cdk/table";
import { NgModule } from "@angular/core";
import {
  MatAutocompleteModule,
  MatButtonModule,
  MatButtonToggleModule,
  MatCardModule,
  MatCheckboxModule,
  MatChipsModule,
  MatDatepickerModule,
  MatDialogModule,
  MatExpansionModule,
  MatFormFieldModule,
  MatGridListModule,
  MatIconModule,
  MatInputModule,
  MatListModule,
  MatMenuModule,
  MatNativeDateModule,
  MatPaginatorModule,
  MatProgressBarModule,
  MatProgressSpinnerModule,
  MatRadioModule,
  MatRippleModule,
  MatSelectModule,
  MatSidenavModule,
  MatSliderModule,
  MatSlideToggleModule,
  MatSnackBarModule,
  MatSortModule,
  MatStepperModule,
  MatTableModule,
  MatTabsModule,
  MatToolbarModule,
  MatTooltipModule,
} from "@angular/material";

@NgModule({
  imports: [
    MatAutocompleteModule,
    MatButtonModule,
    MatButtonToggleModule,
    MatCardModule,
    MatCheckboxModule,
    MatChipsModule,
    MatDatepickerModule,
    MatDialogModule,
    MatExpansionModule,
    MatFormFieldModule,
    MatGridListModule,
    MatIconModule,
    MatInputModule,
    MatListModule,
    MatMenuModule,
    MatNativeDateModule,
    MatPaginatorModule,
    MatProgressBarModule,
    MatProgressSpinnerModule,
    MatRadioModule,
    MatRippleModule,
    MatSelectModule,
    MatSidenavModule,
    MatSliderModule,
    MatSlideToggleModule,
    MatSnackBarModule,
    MatStepperModule,
    MatSortModule,
    MatTableModule,
    MatTabsModule,
    MatToolbarModule,
    MatTooltipModule,
    CdkTableModule
  ],
  exports: [
    MatAutocompleteModule,
    MatButtonModule,
    MatButtonToggleModule,
    MatCardModule,
    MatCheckboxModule,
    MatChipsModule,
    MatDatepickerModule,
    MatDialogModule,
    MatExpansionModule,
    MatGridListModule,
    MatIconModule,
    MatInputModule,
    MatListModule,
    MatMenuModule,
    MatNativeDateModule,
    MatPaginatorModule,
    MatProgressBarModule,
    MatProgressSpinnerModule,
    MatRadioModule,
    MatRippleModule,
    MatSelectModule,
    MatSidenavModule,
    MatSliderModule,
    MatSlideToggleModule,
    MatSnackBarModule,
    MatStepperModule,
    MatSortModule,
    MatTableModule,
    MatTabsModule,
    MatToolbarModule,
    MatTooltipModule,
    CdkTableModule
  ]
})
export class MaterialModule {
}

import { MaterialModule } from "./material.module";

@NgModule({
  imports: [
    CommonModule,
    FormsModule,
    HttpClientModule,
    MaterialModule
  ],
  exports: [
    // common and shared components/directives/pipes between more than one module and components will be listed here.
    CommonModule,
    FormsModule,
    HttpClientModule,
    MaterialModule
  ]
})
export class SharedModule {
}

 <button mat-button>Click me!</button>

 <mat-checkbox>Check me!</mat-checkbox>

 @import "~@angular/material/prebuilt-themes/indigo-pink.css";

 <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">

<button mat-button>
  <mat-icon>face</mat-icon>
  Click me!
</button>
<mat-checkbox>Check me!</mat-checkbox>

 npm install material-design-icons --save

"styles": [
   "node_modules/material-design-icons/iconfont/material-icons.css",
   "src/styles.css"
],

{
    "outputFileName": "out.js",
    "inputFiles": [ "in.js" ],
    "minify": {
        "enabled": true,
        "preserveImportantComments": true
    }
}

 {
    "outputFileName": "output/bundle.css",
    "inputFiles": [
      "css/lib/**/*.css", // globbing patterns are supported
      "css/input/site.css"
    ],
    "minify": {
        "enabled": true,
        "commentMode": "all"
    }
  },

If you are like me, when you start a podcast, you rarely go back to find old ones, which may be out of date.  However, some of Yet Another Podcast is worth a listen even now.  Here are some of the best that are still relevant. 

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. 

These are the customer-reported issues addressed in 15.8.4:

• Constexpr function with explicit (void) parameter crashes MSVC 15.8.0 release.
• TypeScriptLspCodeActionProvider encountered an error and has been disabled.
• The 'Shared Web Components' package did not load correctly.
• Editing CSS with Browser Link enabled can crash Visual Studio.
• Service Fabric Deployment fails in 15.8.0.
• Incorrect error for constexpr pointer to members with VS2017 15.8.
• Constexpr doesn't support __declspec(dllimport) in VS2017 15.8.
• C++ VS 2017 Update 8 difference in member function pointer between C++14 and C++17 modes leads to crashes.
• TestExplorer locking up UI in latest build.
• [WebKit] "Already defined symbol" for static template member definition (regression).
• VS 15.8.0 Internal compiler error.
• Internal compiler error in constexpr function.
• Test Explorer Window remains blank with Express.
• Visual Studio 2017 fails to open on FIPS-enabled machine..
• VS2017 15.8 Internal Compiler Error 'msc1.cpp', line 1518 when evaluating simple constexpr function.
• Fatal error C1001 after update to VS 15.8.0.
• Migrating to VS2017 15.8: Internal compiler error when using constexpr functions as template parameters.
• Internal compiler error when compiling a template function with a constexpr in VC++ 15.8.0.
• Code generated by VC 15.8.1 compiler lead to crash.