This post is the second part of my previous post where we discussed six tips to improve the performance of ASP.NET applications. In this post, we are going to discuss six more tips that could be another round a booster for your application performance. The link to the previous post is included.
The App Builder Blog
We’ve recently been looking a fair bit into the world of wireframes and prototypes and what they can do for the design and development process. However, we are yet to touch upon the history of this discipline, specifically the history of wireframes. In this post we will do just that.
Small multiples — collections of small (obviously) graphics where the same variables are plotted in each graphic but the data in each graphic are conditioned based on another variable (or two) — can be used for similar purposes, with some advantages and some disadvantages.
In this article, we will learn how to create an ASP.NET Web API using the Repository pattern and the Entity Framework code first approach.
Building and hosting a web application on a web server is insanely easy with ASP.NET and IIS. However, many opportunities and hidden configurations can be tweaked to make it a high-performance web application. In this series post, we will discuss some of the most unused or ignored tricks that can be easily applied to any web application.
It’s usually good practice to have automated unit tests while developing your code. Doing so helps you find bugs early in the development cycle and saves you time in the long run.
Before we start to see, how a private method can be unit tested using the MS Test? Let us discuss whether it is a good idea to test a private method or not?
Often, I hear developers ask “What is the ‘controller as’ syntax and how it is different from the $scope object approach of controller creation?” In this post we will learn about controller as syntax and compare it with the $scope object approach of controller creation.
The Liskov Substitution Principle says that the object of a derived class should be able to replace an object of the base class without bringing any errors in the system or modifying the behavior of the base class.
You may have heard that to design a good user experience you first need to understand the users and their needs, but what exactly do you need to know? It comes down to five W and one H question – Who, What, When, Where, Why, and How.