MVC Architecture

MVC or Model View Controller is an architectural style that separates the business from the presentation layer to enable independent development and testing of each. MVC is not a new concept, It has existed right from the nascent days of software development with the first implementation being in SmallTalk in 1979 done by Trygve Reenskaug.

It is relatively new to the Microsoft World though, with the ASP.NET MVC framework being shipped in 2008 compatible with Visual Studio 2008 – .NET Framework 3.5. So what is MVC? MVC divides the application into three parts – The model, View and the controller.

• Controller:- The controller is the heart of the MVC application. It recieves each and every request that is made by the user and responds to it accordingly. It controls the flow of the application.

• Views:- This is the actual UI of the application. The controller controls how the view should be rendered to the browser. Views contain markup, scripts just like an .aspx page

• Model:- Apart from the View and the controller, all the other parts in the application are collective called as the Model. These components are the business and data logic of the application.

A huge advantage of the MVC architecture is that it separates all these three components and makes them completely independent of each other. Hence all of them can be tested separately rather than the case with the webform architecture where testing each component is a pain and mostly we end up doing functional testing for the whole application. This also means modifying one component is far more easy without disturbing the whole application.

Since all the requests are now handled by the controller, we cannot use the postback feature of the web controls like the webform architecture. One of the drawback (or advantage) of MVC is the level of control over HTML rendering that we have. Since we can exactly control how the page will be rendered, we have to write more code to do so. Also you will see more code mixed with Markup, something that ASP.NET eliminated with the help of code behind.

MVC and WebForms are to be seen as two distinct styles which are advantageous to use depending on the scenario, rather than being pitted against each other. If you have a small standalone application to develop with fewer programming resources, a webform based application makes more sense since there is less coding involved. However if you are looking to build an application that would be used and extended by a large number of users, MVC is certainly the way to go.

Reference:http://blog.ganeshzone.net/blog/index.php/tag/mvc/

Difference between http and https

There are some primary differences between http and https, however, beginning with the default port

1) which is 80 for http and 443 for https.

2) Https works by transmitting normal http interactions through an encrypted system,

3) the information cannot be accessed by any party other than the client and end server.

4) There are two common types of encryption layers: Transport Layer Security (TLS) and Secure Sockets Layer (SSL), both of which encode the data records being exchanged.

5)When using an https connection, the server responds to the initial connection by offering a list of encryption methods it supports. In response, the client selects a connection method, and the client and server exchange certificates to authenticate their identities. After this is done, both parties exchange the encrypted information after ensuring that both are using the same key, and the connection is closed. In order to host https connections, a server must have a public key certificate, which embeds key information with a verification of the key owner's identity. Most certificates are verified by a third party so that clients are assured that the key is secure.

6)Https is used in many situations, such as log-in pages for banking, forms, corporate log ons, and other applications in which data needs to be secure. However, if not implemented properly, https is not infallible, and therefore it is extremely important for end users to be wary about accepting questionable certificates and cautious with their personal information while using the Internet.

7)http is a system for transmitting and receiving information across the Internet. Http serves as a request and response procedure that all agents on the Internet follow so that information can be rapidly, easily, and accurately disseminated between servers, which hold information, and clients, who are trying to access it. Http is commonly used to access html pages, but other resources can be utilized as well through http. In many cases, clients may be exchanging confidential information with a server, which needs to be secured in order to prevent unauthorized access. For this reason, https, or secure http, was developed by Netscape corporation to allow authorization and secured transactions.

8)https is identical to http, because it follows the same basic protocols. The http or https client, such as a Web browser, establishes a connection to a server on a standard port. When a server receives a request, it returns a status and a message, which may contain the requested information or indicate an error if part of the process malfunctioned. Both systems use the same Uniform Resource Identifier (URI) scheme, so that resources can be universally identified. Use of https in a URI scheme rather than http indicates that an encrypted connection is desired.

Bubble Tooltip CSS

http://ajax-matters.blogspot.com/2009/01/css-bubble-tooltip.html

Projects

http://www.dotnetspider.com/projects/index.aspx

Chat Application

http://www.aspfree.com/c/a/ASP.NET/Developing-a-Mini-ASPNET-AJAX-Server-Centric-Based-Chat-Application/4/

JavaScript Best Codes

http://www.javascriptfreecode.com/index.htm

http://www.dreamincode.net/code/browse.php?cid=9

Certification Details

http://rajmittal.blogspot.com/search/label/certification

http://en.csharp-online.net/Microsoft_Exam_Preparation_Guides

http://subhashnetworld.blogspot.com/2008/04/microsoft-certification-exam-mcsd.html

Training for Microsoft Certification MCTS - 70-515 (Web
Application Development)

Certification towards: MCTS: .NET Framework 4, Web Applications - Exam
70-515

Duration: One and half month (2 hours per day)

Time: 6:00pm to 8:00pm

Fee: 4000 (Four Thousand Only) for training.

DEMO: June 27th-2011, evening 6:00pm

Address:
SkilledRES, 4th Floor, Uday Mansion, Back to Bank of Baroda, Beside
Yashoda Hospital Lane, Panjagutta.


For assistance call 9908119429.

UPDATE:

Exam 70-536 has been a prerequisite for MCTS on .NET 2.0 and 3.5. It will be removed for .NET 4.0.

Microsoft is trying to streamline the certification process so that we can have a "one exam, one cert" mantra for the MCTS credentials.

What this means is that there won't be upgrade exams for the MCTS because it will only require one exam to get the latest certification.

So, if you pass your MCTS on .NET 3.5 and then later want to get the MCTS Web developer for .NET 4.0, you will only need to take one exam.

FOR ALL MCTS CERTIFICATION EXAM CODES REFER THE BELOW LINK

http://www.microsoft.com/learning/en/us/certification/mcts.aspx#tab2