Hi,

Here is lot of Interview Tips and Tricks are available....

Learn with my posts and share your knowledge here.

Hi,
Get Some asp.net interview questions through this site,
ASP.NET Interview Questions

What are the new features?

ASP.NET controls for Silverlight
ASP.NET MVC model-view-controller (MVC)
ASP.NET Dynamic Data
ADO.NET Entity Framework
ADO.NET Data Services
ASP.NET AJAX

What is ASP.NET controls for Silverlight

You can integrate the rich behavior of Microsoft Silverlight into your Web application by using the familiar model of ASP.NET server controls. The MediaPlayer server control lets you integrate media sources such as audio (WMA) and video (WMV) and take advantage of rich built-in media player skins. The Silverlight server control lets you add your own Silverlight XAML content to ASP.NET pages, using a custom JavaScript type or a Silverlight 2 managed-code XAP package.

What is ASP.NET MVC

ASP.NET MVC provides a framework that enables you to easily implement the model-view-controller (MVC) pattern for Web applications. This pattern lets you separate applications into loosely coupled, pluggable components for application design, processing logic, and display. ASP.NET MVC also greatly facilitates test -driven development (TDD).

What is ASP.NET Dynamic Data

ASP.NET Dynamic Data helps developers build a fully customizable, data-driven app quickly. It provides a rich scaffolding framework that allows rapid data driven development without writing code, yet it is easily extendible using the traditional ASP.NET programming model.

What is ADO.NET Entity Framework

ADO.NET Entity Framework is a new modeling framework that enables developers to define a conceptual model of a database schema that closely aligns to a real world view of the information. Benefits include easier to understand and easier to maintain application code that is shielded from underlying database schema changes.

What is ADO.NET Data Services

ADO.NET Data Services provide new services that find, manipulate and deliver data over the web using simple URIs. Benefits include an easy and flexible way to access data over the web, while enabling the separation of presentation and data access code.

How to Create an ADO.NET Web Data Service

The ADO.NET Data Service framework is comprised of two components. The first component is the runtime itself; this part is constant and it implements URI translation, the Atom/JSON wire formats, and the interaction protocol.

The second component is the data-access layer. Communication between components uses the IQueryable interface with a set of conventions that map common language runtime (CLR) types to the URI/payload patterns used by ADO.NET Data Services.

The first step in creating an ADO.NET Data Service is to select or create a data access layer. The data source will be exposed as a set of REST-based endpoints.

Creating a Local Data Service Using Visual Studio

The steps to create a data service are:
1. Create a Web project.
2. Establish a connection with the database.
3. Create the data service within the Web application.

ADO.NET Data Services are a specialized form of Windows Communication Foundation services, and they can be hosted in various environments. For this CTP release, ADO.NET Data Services must run within ASP.NET sites.

How to Create the Data Services Project

1. Create a Web application project by using the File menu in Visual Studio and choosing New/Project.
2. When the New Project window appears, choose either Visual Basic or Visual C# as the programming language.
3. Select Web for the project type.
4. Select ASP.NET Web Application from the right-hand panel.
5. Type a name for the project, such as SimpleDataService.
6. Click OK.

How to Create the Entity Data Model

1. Create an Entity Data Model (EDM) based on your database using the ADO.NET Entity Framework.
2. Right-click the project name in Solution Explorer and select Add New Item.
3. When the Add New Item window appears, choose ADO.NET Entity Data Model.
4. Name the data model Northwind. Northwind.edmx is the generated file name. The schema of the EDM being created maps one-to-one1 with the Northwind sample database.
5. In the Entity Data Model Wizard, select Generate from Database, and click Next.
6. Create a new connection to the database by using the New Connection button, or use one of the available databases if you have one pre-configured. Click Next.
7. In the last window, the wizard presents the list of tables, views, and stored-procedures available from the database. Leave the default selection for tables and, for simplicity, uncheck views and stored-procedures. Click Finish to close the wizard.

The wizard generates files to represent the database metadata and add them to the project. In the rest of the step-by-step guide, it is assumed that you are using the Northwind example database, so the database connection created here points to Northwind.

What are the Features of ASP.NET Dynamic Data

ASP.NET Dynamic Data provides the following features to support the rapid development of data-driven Web applications:

* Built-in Web application infrastructure to support the creation of a data-driven Web applications without having to create pages or control code. This scaffolding includes the following elements:
o A data model that you generate by using the Object-Relational Mapping (ORM) designer. The designer generates the classes that model the underlying database.
o Page templates that are used by the scaffolding to provide the default views of data.
o Dynamic Data fields for rendering individual data types.
o Data-model attributes that enable you to customize rendering.
o Built-in data validation based on the database schema.
* Dynamic Data configuration settings that you can customize in the Web.config file.
* Seamless integration with existing ASP.NET data controls for customization. This enables you to adopt an incremental development process while migrating toward adoption of the Dynamic Data controls.

What are the features of ASP.NET controls for Silverlight

The Silverlight 2 SDK Beta 1 supports the following ASP.NET controls for Silverlight:

* System.Web.UI.SilverlightControls.MediaPlayer server control
* System.Web.UI.SilverlightControls.Silverlight server control

What is the MediaPlayer Server Control

The MediaPlayer server control lets you integrate media sources such as audio (WMA) and video (WMV) into your Web application, without requiring any knowledge of XAML or JavaScript. The MediaPlayer control can use pre-built skins, or you can create custom skins. For example, you can reference a custom XAML document that is generated through Microsoft Expression Encoder and that supports captions, chapters, and markers in the media source. When you configure the MediaPlayer control to reference a pre-built skin, the associated XAML document is copied into the project. The MediaSkinSource property of the MediaPlayer is also set to point to the referenced skin. For more information about Expression Encoder, see the Microsoft Expression Encoder Web site.

The control also generates a client JavaScript object that manages user interaction with the player. The control generates the appropriate markup and code to display and control media.

What is the Silverlight Server Control

The Silverlight server control enables you to reference XAML that you provide. If you use managed code with the XAML, the Silverlight control provides a way to embed the XAML application in the Web page.

What are three main components of the Model View Controller (MVC) architectural pattern

The MVC framework includes the following components:

* Models. Model objects are the parts of the application that implement the logic for the application's data domain. Often, model objects also retrieve and store model state in a database. For example, a Product object might retrieve information from a database, operate on it, and then write updated information back to a Products table in SQL Server.
Note

In small applications, the model is often a conceptual separation rather than a physical one. For example, if the application only reads a data set and sends it to the view, the application does not have a physical model layer and associated classes. In that case, the data set takes on the role of a model object.
* Views. Views are the components that display the application's user interface (UI). Typically, this UI is created from the model data. An example would be an edit view of a Products table that displays text boxes, drop-down lists, and check boxes based on the current state of a Product object.
* Controllers. Controllers are the components that handle user interaction, manipulate the model, and ultimately select a view to render that displays UI. In an MVC application, the view only displays information; the controller handles and responds to user input and interaction. For example, the controller handles query-string values, and passes these values to the model, which in turn queries the database by using the values.

Advantages of an MVC-Based Web Application

The ASP.NET MVC framework offers the following advantages:

* It makes it easier to manage complexity by dividing an application into the model, the view, and the controller.
* It does not use view state or server-based forms. This makes the MVC framework ideal for developers who want full control over the behavior of an application.
* It uses a Front Controller pattern that processes Web application requests through a single controller. This enables you design an application that supports a rich routing infrastructure. For more information, see Front Controller on the MSDN Web site.
* It provides greater support for test driven development (TDD).

Advantages of a Web-Forms-Based Web Application

The traditional Web-forms based framework offers the following advantages:

* It supports an event model that preserves state over HTTP, which benefits line-of-business Web application development. The Web-forms-based application provides dozens of events that are supported in hundreds of server controls.
* It uses a Page Controller pattern that adds functionality to individual pages. For more information, see Page Controller on the MSDN Web site.
* It uses view state or server-based forms, which can make managing state information easier.

Features of the ASP.NET MVC Framework

The ASP.NET MVC framework provides the following features:

* Separation of application tasks (input logic, business logic, and UI logic), testability, and test-driven development (TDD) by default. All core contracts within the MVC framework are interface-based and can be tested by using mock objects, which are simulated objects that imitate the behavior of actual objects in the application. You can unit-test the application without having to run the controllers in an ASP.NET process, which makes unit testing fast and flexible. You can use any unit-testing framework that is compatible with the .NET Framework.
* An extensible and pluggable framework. The components of the ASP.NET MVC framework are designed so that they can be easily replaced or customized. You can plug in your own view engine, URL routing policy, action-method parameter serialization, and other components. The ASP.NET MVC framework also supports using existing Dependency Injection (DI) and Inversion of Control (IOC) container models. DI allows you to inject objects into a class, rather than relying on the class to create the object itself. IOC specifies that if an object requires another object, the first objects should get the second object from an outside source such as a configuration file. This facilitates testing.
* A powerful URL-mapping component that lets you build applications that have comprehensible and searchable URLs. URLs do not have to include file-name extensions, and are designed to support URL naming patterns that work well for search engine optimization (SEO) and representational state transfer (REST) addressing.
* Support for using the markup in existing ASP.NET page (.aspx files), user control (.ascx files), and master page (.master files) markup files as view templates. You can use existing ASP.NET features with the ASP.NET MVC framework, such as nested master pages, in-line expressions (<%= %>), declarative server controls, templates, data-binding, localization, and so on.
* Support for existing ASP.NET features. ASP.NET MVC lets you use features such as forms and Windows authentication, URL authorization, membership and roles, output and data caching, session and profile state management, health monitoring, configuration system, the provider architecture, and other areas of ASP.NET.