What an Intermediate ASP.Net Developer Should Know

by **BIT0112-Rokon** Fri Sep 16, 2011 11:14 pm

Prerequisites

An intermediate ASP.Net application will require more sophistication so a more advanced skill set is required. The hurdle of being familiar with programming and/or VB/C# has been cleared, but another obstacle stands in the way. In order to be an intermediate ASP.Net developer, the principles of object oriented and structured programming must be familiar to you. Without those skills, tackling the tasks below will be very difficult.

Skills to Master

Data Model: A beginning DotNet developer will take his SQL queries and bind them directly to the UI. However, more
advanced developers build objects to store that data. In fact, an entire model on which data can be mapped is what intermediate developers build and use.
Binding the Data Model: Web Forms and MVC are different, but both architectures require that data be bound to the
view. For an intermediate developer, your task is to bind your data model to the correct view. Instead of binding the specific data items from the query, you will be binding the data object instead.
Basic Business Logic: Validating data was the only appreciable logic that the beginning ASP.Net application had. Your goal here is to build a little more sophisticated business logic. This skill requires some explaining, which I will do in the next section.

What to Build

The skeleton already exists from the beginner’s application, so there is no need to start from scratch. This application will be tweak the previous one, which should serve as a good lesson as to why good practices are a lifesaver in the end. Considering that side note, let us delve into what this application should look like.

First, you will need to examine your data and figure out how it is structure. Depending on the data this could be a straightforward process or it could be incredible tedious. Either way, a data model should emerge from this study. The next step is constructing that data model, which should be easier than the first process. After you have completed the data model, the queries need to be mapped to those classes. At the completion of that step, intermediate database
interaction has been mastered.

Merely interacting with database is not worth a whole lot. Besides, changing your queries to map to classes breaks your code. The final step rectifies that problem by binding those objects to the view. Now your software is function again.

The final piece of the puzzle as well as the least clear is the concept of business logic. In the previous application, logic consisted of data validation and database operations. The goal here is to add some more sophistication, but where and what should be added? Starting out with simple extensions is best. Ordering forms in a workflow or making certain things available based on persistent, changeable states are good examples. Storing user names, passwords, and using those to authenticate is also a reasonable hurdle. Try to tackle as least one of those suggestions. If you able to do so, then you are capable of
building intermediate ASP.Net applications.

This post was first published at Code Explosion Blog and written by Collin Rusk