Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
.NET Core 2.0 By Example

You're reading from   .NET Core 2.0 By Example Learn to program in C# and .NET Core by building a series of practical, cross-platform projects

Arrow left icon
Product type Paperback
Published in Mar 2018
Publisher Packt
ISBN-13 9781788395090
Length 458 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (2):
Arrow left icon
Neha Shrivastava Neha Shrivastava
Author Profile Icon Neha Shrivastava
Neha Shrivastava
Rishabh Verma Rishabh Verma
Author Profile Icon Rishabh Verma
Rishabh Verma
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Getting Started FREE CHAPTER 2. Native Libraries in .NET Core 3. Building Our First .NET Core Game – Tic-Tac-Toe 4. Let's Chat Web Application 5. Developing the Let's Chat Web Application 6. Testing and Deploying – The Let's Chat Web Application 7. To the Cloud 8. Movie Booking Web App 9. Microservices with .NET Core 10. Functional Programming with F# 11. Other Books You May Enjoy

Handy things to know


It's important for us to understand that there are fundamental architecture differences between ASP.NET and ASP.NET Core. A few of the important ones are listed here:

  • An important difference between ASP.NET and ASP.NET Core is that ASP.NET Core doesn't have a request queue, unlike ASP.NET. The RequestQueue class which resides in the System.Web namespace is designed to prevent thread pool starvation in ASP.NET. This no longer exists in ASP.NET Core, so as you can rightly guess, there can be thread pool starvation if we do not write proper code. Just so that we are on the same page, starvation describes a situation where a thread is unable to gain regular access to shared resources and is unable to make progress. This happens when shared resources are made unavailable for long periods by greedy long running threads. For example, suppose an object provides a synchronized method that often takes a long time to return. If one thread invokes this method frequently, other threads...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image