
Sign up to save your podcasts
Or
On today’s episode, Scott Hunter joins your host, Jeffrey Palermo, to discuss DevOps capabilities in Azure. Scott is the Director of Program Management for .NET at Microsoft. When Scott first joined Microsoft back in 2007, he was working on the ASP.NET team.
As the Director of Program Management of .NET, he and his team build .NET Core, .NET Framework, ASP.NET, Entity Framework, managed languages (C#/F#/VB), as well as the Web and .NET Tooling for Visual Studio.
Join Scott Hunter and Jeffrey as they take you through the differences between .NET Core and .NET Framework, when and why you should move to .NET Core 3.0 in the future, how .NET Standard bridges the gap between these two, where all the different architectures fit into the .NET ecosystem, and an update and overview on WebAssembly and Blazor. Scott and Jeffrey also give you a preview of their upcoming book, .NET DevOps for Azure, and their motivation behind it.
Topics of Discussion:
[:46] Jeffrey introduces Scott and welcomes him to the show!
[2:46] Scott gives an overview of what his team at Microsoft builds.
[4:10] What is .NET Core 3.0 and when should people on .NET Framework consider moving over to it? What’s the difference between the two?
[11:42] How should we think of .NET Core 3.0 and .NET Framework, moving forward?
[13:20] How .NET Standard bridges the gap between .NET Core and .NET Framework, opening up possibilities.
[16:08] Scott gives an overview and update on WebAssembly and Blazor — an experimental project utilizing .NET Core.
[20:55] Options that will be available with the .NET Core 3.0 release.
[25:25] A word from Azure DevOps Podcast’s sponsor: Clear Measure.
[25:52] Some benefits of Blazor.
[28:00] Would you still be deploying as an Azure website when using Blazor or does it have any changes to the deployment configuration in Azure?
[28:38] Is it mandatory to use SignalR Service or are Blazor apps baked in with the framework?
[30:50] With so many options in the .NET ecosystem, where do all these architectures land? For example, monolith vs. microservices.
[37:24] Scott and Jeffrey give a preview of their upcoming book, .NET DevOps for Azure, and the motivation behind it.
[42:36] What Scott recommends listeners follow-up on after today’s episode.
Mentioned in this Episode:
Azure DevOps
Clear Measure (Sponsor)
.NET Core 3.0
Blazor
WebAssembly
Mono
Azure Kubernetes Service (AKS)
SignalR Service
Monolith vs. Microservices
.NET Architecture Guides
DOT.NET
Want to Learn More?
Visit AzureDevOps.Show for show notes and additional episodes.
4.5
2020 ratings
On today’s episode, Scott Hunter joins your host, Jeffrey Palermo, to discuss DevOps capabilities in Azure. Scott is the Director of Program Management for .NET at Microsoft. When Scott first joined Microsoft back in 2007, he was working on the ASP.NET team.
As the Director of Program Management of .NET, he and his team build .NET Core, .NET Framework, ASP.NET, Entity Framework, managed languages (C#/F#/VB), as well as the Web and .NET Tooling for Visual Studio.
Join Scott Hunter and Jeffrey as they take you through the differences between .NET Core and .NET Framework, when and why you should move to .NET Core 3.0 in the future, how .NET Standard bridges the gap between these two, where all the different architectures fit into the .NET ecosystem, and an update and overview on WebAssembly and Blazor. Scott and Jeffrey also give you a preview of their upcoming book, .NET DevOps for Azure, and their motivation behind it.
Topics of Discussion:
[:46] Jeffrey introduces Scott and welcomes him to the show!
[2:46] Scott gives an overview of what his team at Microsoft builds.
[4:10] What is .NET Core 3.0 and when should people on .NET Framework consider moving over to it? What’s the difference between the two?
[11:42] How should we think of .NET Core 3.0 and .NET Framework, moving forward?
[13:20] How .NET Standard bridges the gap between .NET Core and .NET Framework, opening up possibilities.
[16:08] Scott gives an overview and update on WebAssembly and Blazor — an experimental project utilizing .NET Core.
[20:55] Options that will be available with the .NET Core 3.0 release.
[25:25] A word from Azure DevOps Podcast’s sponsor: Clear Measure.
[25:52] Some benefits of Blazor.
[28:00] Would you still be deploying as an Azure website when using Blazor or does it have any changes to the deployment configuration in Azure?
[28:38] Is it mandatory to use SignalR Service or are Blazor apps baked in with the framework?
[30:50] With so many options in the .NET ecosystem, where do all these architectures land? For example, monolith vs. microservices.
[37:24] Scott and Jeffrey give a preview of their upcoming book, .NET DevOps for Azure, and the motivation behind it.
[42:36] What Scott recommends listeners follow-up on after today’s episode.
Mentioned in this Episode:
Azure DevOps
Clear Measure (Sponsor)
.NET Core 3.0
Blazor
WebAssembly
Mono
Azure Kubernetes Service (AKS)
SignalR Service
Monolith vs. Microservices
.NET Architecture Guides
DOT.NET
Want to Learn More?
Visit AzureDevOps.Show for show notes and additional episodes.
378 Listeners
262 Listeners
246 Listeners
286 Listeners
154 Listeners
42 Listeners
584 Listeners
630 Listeners
200 Listeners
143 Listeners
987 Listeners
182 Listeners
63 Listeners
137 Listeners
48 Listeners