Learn .NET in 60 Days - Part 2 (13 Labs)

In case you have missed labs 1 to 13 you can click here to see them: Part 1: - Learn .Net and C# in 60 days Part 1 (13 labs).

It has been nearly a year now since beginning this resolution of teaching C# for free on csharpcorner.com and with nearly 50 videos in the you tube channel (www.youtube.com/LearnDotnet60days ) and every video nearly 30 minutes we are reaching our milestone gradually.

There is one saying that says that if you do good work, people recognize your effort. It was an awesome day when Mr. Scott Guthrie (VP Microsoft Developer division) tweeted about our initiative in his tweet. Thanks to Mr. Mahesh Chand sir and csharpcorner.com to provide a platform so that this initiative is visible to the C# developer community.


So we continue as usual our good work, ensuring that beginners have the opportunity to learn C# for free. Please note that we are humans so we cannot really record 100 videos in one day, it takes time to provide quality output. So your patience will definitely pay off.

Said and done even if you practice 50 videos that we have currently uploaded on the channel, you are almost an awesome C# developer.

So to begin learning .NET and C# in 60 days we started by creating our First program in C#, we  then took some data from the console application , did some exception handling, created a calculator program and finally we talked about classes and objects in C#.

In case you have missed it you can see the complete 1 to 13 labs series by clicking on Part 1: - Learn .Net and C# in 60 days Part 1 ( 13 labs)

So the following continues with the next 13 labs of Learn ".NET and C# in 60 days". (Note: just click on the images to view the videos.)


Lab 14: - In this lab we will connect to SQL Server and get data.While doing this practice we will get acquainted with ADO.NET components, like connection, command and data reader.


Lab 15: - In this lab we will insert data from the UI to SQL Server. So we will create a insert SQL statement and give it to the SQL commandobject.


Lab 16: - In Lab 14 and Lab 15 we will connect to SQL Server and insert and read data. When we connect to SQL Server we need to specify a SQLserver connection string. In both of these labs, the SQL connection string is hard-coded in the program. Hard coding things in programs make the application less flexible. So in case the SQL Server location changes we need to recompile the entire application. In lab 16 we see how to make the connection string configurable by storing it in a XML configuration files rather than hard-coding it in the C# code.


Lab 17: - In this lab we will implement delete functionality by writing the delete SQL command in the ADO.NET command object.


Lab 18: - In this lab we see how to select data when a user clicks o nthe data grid hyper link. Once the data is displayed we will also update data by using the UPDATE SQL command using the ADO.NET command object.


Lab 19: - Until Lab 18 our data entry project is one big heavy piece. So if we want to change the business logic, we must change it in many places. If we want to do some amendments in SQL we must again change all that in many places. So if we can break this project into smaller layers we will be in a better shape to manage it. In this lab we will break the project into a 2-layered architecture, the first layer will have UI + business logic and the second layer will have the SQL part i.e. data access.


Lab 20: - Until Lab 19 we were working only with Windows applications. But now the trend is more web applications rather than Windows application. So in Lab 20 we will create an ASP.NET web application UI that will interact with the customer data entry database.


Lab 21: - In this Lab we will connect the ASP.NET Web application UI with the data access layer.






Lab 22: - In this lab we will demonstrate insert, update and delete functionality for the ASP.NET web application UI.


Lab 23: - Until Lab 22 our project is divided into two layers, one is the UI + Business logic and the other is the data access layer. In other words it's a 2-tier architecture. So if we change the SQL part we do not need to update the UI and business logic. But the problem with the 2-tier architecture is that the business logic still resides in the UI part. So if we want to modify the business logic then we need to make changes in the UI section as well. In this lab we will convert the 2-tier architecture to a 3-tier architecture. In other words we will create 3 layers (UI , business logic and data access).


Lab 24: - Security is of the most important aspect of any application. In this section we will see how to implement security in Windows applications.


Lab 25: - Lab 24 demonstrates how to implement security in Windows applications. But when we talk about security in web applications it's a bit different compared to Windows. So in this lab we will implement Web security using Forms Authentication.


Lab 26: - Validation is an important activity in any application. We often encoutnher complex validation, like email address, phone number etc.The complexity of validations can be minimized using Regular Expressions.In this video we will demonstrate how to implement email validation easily using a regular expression (REGEX).


Lab 27: - Until this lab we were concentrating on the application aspect only. But we have still not looked at to the database side. Our database currently is completely flat that can lead to redundant and duplicate data. So in this lab we will work on how to apply normalization rules to make our database more structured so that we can avoid redundant and duplicate data.

I would like to thank personally http://www.questpond.com/ who took care to feed me so that I can record these videos for free for C# developers. Please do visit questpond.com for .NET and C# interview question video series.  

Similar Articles