Posts

Showing posts from June, 2012

ASP.NET MVC Vs ASP.NET WebForms

Here are some points that differentiate ASP.NET WebForms from ASP.NET MVC: ASP.NET WebForms ASP.NET MVC Uses the ‘Page Controller’ pattern. Each page has a code-behind class that acts as a controller and is responsible for rendering the layout. Uses the ‘Front Controller’ pattern. There is a single central controller for all pages to process web application requests and facilitates a rich routing architecture Uses an architecture that combines the Controller (code behind) and the View (.aspx). Thus the Controller has a dependency on the View. Due to this, testing and maintainability becomes an issue. ASP.NET MVC enforces a "separation of concerns". The Model does not know anything about the View. The View does not know there’s a Controller. This makes MVC applications easier to test and maintain. The View is called before the Controller. Controller renders View based on actions as a result of the User Interactions on the UI. At its core, you ‘canno

Advantages of MVC Model

Advantages of MVC Model Enable clean separation of concerns (SoC) . Enable full control over the rendered HTML. Enable Test Driven Development (TDD) (built with TDD in mind). SEO and REST friendly URL. Easy integration with JavaScript frameworks. Support third-party view engines such as NVelocity, Brail, NHaml. No ViewState and PostBack events. Follows the stateless nature of web. Extensible and Pluggable framework.  Ideal platform for Web 2.0 applications.

MVC Fundamentals

A .  3 Loosely Coupled main components of An MVC Application Input Logic ---------- belongs to ---------- CONTROLLER. UI Logic -------------- belongs to ---------- VEIW. Business Logic------- belongs to ---------- MODEL.       B.     Testing individual loosely Coupled components are Easier. C.      MVC does not use VEIW-STATE or SERVER-BASED forms, thus making developers to have full control over the     Application Behavior. D.     MVC is good for applications which need high Degree of control over the Application Behavior. E.      ASP.NET uses “Page Controller” pattern that adds functionality to individual pages. F.       Managing State Information is easier for ASP.NET. G.     ASP.NET enables rapid application development. H.     The components of ASP.NET (like the page class, controls, etc. ) are tightly integrated and usually requires less code than MVC. I.        Components of MVC can be easily replaced / customized. You can plug-in your

MSMQ - Overview

1) Overview of MSMQ MSMQ stands for Microsoft Messaging Queue. MSMQ works on disconnected or connected mode and provides Asynchronous Programming. If client is disconnected from network, in that scenario, MSMQ is the most preferrable method because in this case the Server does not need to wait for client to read the data and send back the acknowledgement to server. (sample code in this article are tested on Visual Studio 2008) (2) Verifying whether MSMQ is installed on your system Navigate to "Services" by executing "Services.msc" in Run menu, then Sort on Name and Scroll down to find Message Queuing. If it is not there, that means MSMQ is not installed. (3) MSMQ Setup Control Panel -- Add/Remove Windows Components -- Select Message Queuing – Next (and follow in the instructions given on the subsequent windows) This will install MSMQ in your system and it can be verified by Navigating to Computer Management also as given below… Control panel -- Adm

RDBMS Vs OODBMS

An Object-Oriented Database Management System (OODBMS), sometimes referred as Object Database Management System (ODMS) is a Database Management System (DBMS) that supports modeling and creation of data as objects. OODBMS provides support for object classes, class property and method inheritance by sub classes and their objects. A Relational Database Management System (RDBMS) is also a DBMS but, that is based on the relational model. Most popular DBMSs currently in use are RDMSs. As mentioned earlier RDBMS is based on the relational model and data in a RDMS are stored in the form of related tables. So, a relational database can simply be seen as a collection of one or more relations or tables with columns and rows. Each column corresponds to an attribute of the relation and each row corresponds to a record that consists of data values for an entity. RDMSs are developed by extending hierarchical and the network models, which were two previous database systems. Main elements of a RD