It took me a while to get my head around the new .NET Standard which is going to affect the monikers that are going to be used in ASP.NET Core. I felt the need to simplify it as much as possible primarily to help me remember how it works :-) Portable Class Libraries The .NET Standard can be seen as the next version of portable class libraries (PCLs). The main disadvantage of a PCL is that it is tied up front to one or more .NET platforms. You see the .Net platforms listed in the first column of the table below. Imagine you create a PCL now and configure it to support Silverlight and .Net Framework 4.6. Then...
Here are some upcoming public events I'll speak at. If you'd like a private event around one of these topics please contact me
- Pluralsight Live: 28 August, Salt Lake City — Understanding Modern Cloud Architecture
- MCT Global Summit: 22 October, Bruehl Germany — ASP.NET Core Security
- Update Conference: 22 November, Prague — ASP.NET Core Security + SignalR
- DotNet Conference: 28 November, Cologne Germany — ASP.NET Core Security
Don't have Pluralsight? Apply here to watch my courses below and many others for free!
- Getting Started with ASP.NET Core SignalR
- A Practical Start with React
- Understanding ASP.NET Core 2.x
- Getting Started with ES2017/ES8
- Scaling Applications with Microservices and NServiceBus 6
- Understanding ASP.NET Core Security
- A Practical Start with TypeScript
- Scaling Applications with Microservices, MassTransit and RabbitMQ
- Scaling Applications with Microservices and NServiceBus 5
- Introduction to Graph Databases and Neo4j
- Creating Mobile Apps: Native, Hybrid or Cross Platform?