There is a lot of activity happening around ASP.NET 5. To try to keep things straight, I thought I would create a mind map of my current understanding. The image below starts at ASP.NET 5 and branches out to concepts around the growing ecosystem.
What do you think? Is my mind map anywhere close to what you are thinking about ASP.NET 5?
I am starting to develop more with ASP.NET 5. My journey through beta 5 to 8 has been an interesting one, with much left unexplored. This post hopes to poke fun at me. Developers may receive insight into what it is like transitioning to the new platform.
The drumbeat gets louder as we approach a Release Candidate. It is hard not . . .
Stuntman is a .NET library built by RIMdev to give developers access to a set of authentication credentials at development time. It gives me the ability to mock quickly, while not having to deal with a complicated authentication mechanism. I wanted to write a simple ASP.NET 5 banking application utilizing Entity Framework 7. The application . . .
developing and deploying a "minor" feature
Small trees sometimes have long roots. In the case of software development, what may seem like a little feature can need a lot of work. A third party partner requested a link to appear on the client user interface. This write-up aims to clarify what went into executing and deploying a simple link and why it is not as easy as it seems.
The . . .
I was paying a bill today and after submitting the form, I saw a successful confirmation page. There on the confirmation page was a message displayed in retina burning red.
Do Not Refresh The Page
This was an expensive payment. I assume that refreshing the page would cause a double billing issue. As a seasoned web developer, I have learned . . .
Our software deployment process depends on three environments: development, quality assurance (QA), and production. Each of those environments has its own set of actors and resources. In our case our resources can be simplified to applications and databases. Our actors include but are not limited to developers, QA engineers, and database . . .
It's not very often, but there are times when a stored procedure just works a little better than LINQ. Complexity for developers can be decreased while performance can be dramatically increased for users. In those very rare cases, it may make sense to return more than one result set from a stored procedure. This post will show you how to . . .