Please log in to watch this conference skillscast.
ASP.NET 5 is the new kid on the block, and it’s here with a lot of new, unfamiliar features and concepts. As a developer, it’s not yet clear why you should start developing on ASP.NET 5 or, more importantly, why you should move an exsisting, healthy project to it. I hear a lot of Questions like: "wow, it wasn’t like that before, why has it changed?" "I’m not familiar with these concepts, so should I stick with [the thing that I am using now]?".
In this talk, I’ll cover the reasons why you should start considering ASP.NET 5 by boiling it down to the tried-and-tested format: 10 top features. We’ll cover everything from new project structures to unified MVC and Web API frameworks, complete with samples and clear explanations of how these things are going to affect the way you code and the way you build projects. Along the way, we’ll cover other little gems like the new Configuration framework.
By the end of the talk, the advantages - and potential pitfalls - of using ASP.NET 5 in terms of both runtime and development process should be crystal clear, and you’ll be able to work out when’s the right time to start using the latest shiny Microsoft bits.
YOU MAY ALSO LIKE:
- Getting Into the Zero Downtime Deployment World (SkillsCast recorded in June 2019)
- Build High Performance Stream Processing and Workflows with TPL Dataflow (Online Meetup on 8th October 2020)
- What’s New in .NET Core 3.0 and .NET 5.0 for Performance and Memory-Aware Folks? (SkillsCast recorded in October 2019)
- Pragmatic Memory Management (SkillsCast recorded in October 2019)
ASP.NET 5: How to Get Your Cheese Back
Tugberk is a self-motivated software developer who craves to create great software products and systems and build effective development teams with a decade of software development and technical leadership experience. He is passionate about knowledge sharing and has been trying to do his best by speaking at conferences, writing blog posts, establishing collaboration on open source projects, and authoring a book. He cares about reliability, observability and scalability of the software products he works on as much as caring about the day-to-day happiness, effectiveness, and productivity of the team he works as part of. He also aims to strive for the balance required to have a stable, maintainable and architecturally-accurate software product, and being on the market fast with an iterative approach.