CSS Friendly Menu Control in ASP.NET 4.0

CodeProject
It is very much easier to apply CSS when we have ul,li elements as the HTML content. If we look into ASP.NET Menu Control till Version 3.5, its render as Table-TR-TD Tag. Though Table/Tr/Td is quite useful to display tabular data but sometime creates a big problem when we need to do more work with CSS. To overcome this problem we generally used CSS Friendly adapter to render the ASP.NET Control in ul/li mode.

ASP.NET 4.0 makes the things easier for web developer by providing "RenderingMode" properties. Here we can specify RenderMode of a ASP.NET Menu control. Which define the what will be the HTML Render Content Type. Bydefault mode is "List" which means control will be render as ul/li.



Read Complete Article @ Abhijit's World Of .NET
CSS Friendly Menu Control in ASP.NET 4.0

ViewState Control in ASP.NET 4.0

CodeProject
View State is one of the most important and useful client side state management mechanisms. It can store the page value at the time of post back (Sending and Receiving information from Server) of your page. ASP.NET pages provide the View State property as a built-in structure for automatically storing values between multiple requests for the same page.

we generally used “EnableViewState” Properties for both Page Level and Server Control Level to maintain the view state. Till ASP.NET 3.5 Version, Page Level view state control treat as highest priorities. Which means If we set EnableViewState= “False” in page level that will automatically derived by all the server side control. In that case if we set “EnableViewState=”True”” for any server side control will treat as false, as we have defined them “False” in Page Level.Here is one complete article on ASP.NET 2.0/3.5 View State , which may helpful for you

Now, let’s have a look into the changes in ViewState Control in ASP.NET 4.0. There is a massive change in View State Control in ASP.NET 4.0 which is very much helpful for developer also. Asp.net 4.0 added a new property to Page object and server controls called ViewStateMode.

IntelliTrace Debugging - Video Demo

Recently I have published one complete tutorial on Visual Studio 2010 Debugging. Which covered almost all main features of debugging in Visual Studio 2010 like Basic of Breakpoints,  breakpoint labeling, data tips, multithreaded debugging, and parallel debugging and IntelliTrace debugging. You can read the complete article from My Blog or from CodeProject.

While preparing the article I had created one small video on IntelliTrace Debugging which will show you the demo of using IntelliTrace Debugging.  Hope you will enjoy this video.

MVP (Most Valuable Professional) 2010 - Code Project

I have recognized by MVP (Most Valuable Professional) by Code Project again for the year 2010. This is second time I have been awarded with MVP. I have received MVP because of Contribution to the Code Project Forum over the year 2009.
I would like to congratulate all the MVP Winners 2010.
I would like to thank all my readers, friends and well wishers and thanks to Chirs Maunder(Co- Founder of Code Project), Sacha Barber , Rajesh R Subramanian , Christian Graus , Abhishek Sur and all CP Members

Beginners Guide’s to ASP.NET MVC Framework – Part 1 of n

CodeProject
This article describes overview of ASP.NET MVC Framework , MVC Control Flow etc.

This article is the Part 1 of the ASP.NET MVC Framework series.  In this article I have describes very basic over view of MVC Framework and the control flow of MVC. I will write a few articles in this series which will help all the beginners to move ahead. This article is only about what MVC is.

Overview

The Model-View-Controller (MVC) design pattern is an architectural design patterns for any standard development that separates the components of an application. This allows application to handle very flexible and extensible and easy to handle. ASP.NET MVC Framework is also one of the standard web development frameworks which separate the components of web development application different components.

ASP.NET MVC Framework having three main components

1. Model


2. View


3. Controller

Model: The model manages the behavior and data of the application domain, responds to requests for information about its state from the view, and responds to instructions to change state (usually from the controller).

View: This represent the presentation layer of the web application. The view manages the display of information based on the data of model that is requested by controller.

Controller: Controller handles the user interaction with the web application.  User request comes through controller to model and manipulate the records from it and then render the data using View to UI.

Below diagram showing the overview of these three components

Request Flow for ASP.NET MVC Framework

1. Request comes from User to Controller


2. Controller processes request and forms a data Model


3. Model is passed to View


4. View transforms Model into appropriate output format


5. Response is rendered to Browser

Above picture showing you the actual flow of ASP.NET MVP Framework.  Request comes from client to Controller and controller decided which model to used and based on that data rendered into browser.

Now, just have a closer look into to the MVC Flow,



In the next article I will give the explanation of each of every step. You just need to remember these are the basic flow of an MVC Application.

ASP.NET Web Forms and  MVC

MVC is not a replacement if ASP.NET Web Form based development. This seats on the top of ASP.NET Development.  MVC Framework simply divides the overall application architecture into three components.

For More information on the basic of MVC Framework please read :
ASP.NET MVC Overview (C#)

Summary

This is the startup article for MVC beginners. Many more to come. Where I will explain details of each of them with sample application. Finally there would be a complete ASP.NET project on MVC Framework. Hope this series will be helpful for all.