Skip to main content

ASP.NET Web API 2 Request Pipeline

I remember a time where ASP.NET WebForms was mainstream and ASP.NET MVC and Web API still had to be invented. To do a good a job as an ASP.NET WebForms developer you needed deep understanding of the ASP.NET WebForms page lifecycle. (I even got some related interview questions at the time).

These times have gone and now you should understand ASP.NET MVC and Web API both having their own lifecycle. Here is a great poster explaining the ASP.NET Web API Message Lifecycle:

image

And a similar one for ASP.NET MVC:

image

Must print material! Smile

Labels:

Popular posts from this blog

XUnit - Assert.Collection

A colleague asked me to take a look at the following code inside a test project: My first guess would be that this code checks that the specified condition(the contains) is true for every element in the list.  This turns out not to be the case. The Assert.Collection expects a list of element inspectors, one for every item in the list. The first inspector is used to check the first item, the second inspector the second item and so on. The number of inspectors should match the number of elements in the list. An example: The behavior I expected could be achieved using the Assert.All method:
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Lehman’s Laws of Software Evolution

In the world of software engineering, the Lehman's Laws of Software Evolution are widely recognized as a fundamental framework for understanding how software systems evolve over time. These laws were introduced by British computer scientist, Meir Lehman, in the 1980s(!) in his paper “Programs, Life Cycles, and Laws of Software Evolution”, and they remain relevant to this day. Lehman's Laws describe how software systems evolve and how they can be managed over their lifespan. In this blog post, we will explore these laws in detail and their significance in software development. From the paper : The first law of software evolution states that software systems must evolve or they will become progressively less useful . This law recognizes that software is not static and unchanging, but instead must adapt and grow to meet changing user needs and technological advancements. Failure to evolve software systems can result in decreased usefulness or even obsolescence. This means
Read more