LINQ defines standard query operators that allow code written in LINQ-enabled languages to filter, enumerate, and create projections of several types of collections using the same syntax. Such collections may include arrays, enumerable classes, XML, datasets from relational databases, and third party data sources. The LINQ project uses features of version 2.0 of the .NET Framework, new LINQ-related assemblies, and extensions to the C# and Visual Basic .NET languages. Microsoft has distributed a preview release of LINQ, consisting of those libraries and compilers for C# 3.0 and Visual Basic 9. Other languages, such as F# and Nemerle, have also announced preliminary support.

Yes.  If you are debugging via Visual Studio.NET, just go to Immediate window.

CorDBG - command-line debugger.  To use CorDbg, you must compile the original C# file using the /debug switch.                                                                                                                                 DbgCLR - graphic debugger.  Visual Studio .NET uses the DbgCLR.

Test plan tree can include several type of tests
Manual test scripts
Win Runner test scripts
Batch of Win Runner test scripts
Visual API test scripts
Load Runner scenario scripts and Vuser scripts

To access an XML Web service from a client application, you first add a Web reference, which is a reference to an XML Web service. When you create a Web reference, Visual Studio creates an XML Web service proxy class automatically and adds it to your project. This proxy class exposes the methods of the XML Web service and handles the marshalling of appropriate arguments back and forth between the XML Web service and your application. Visual Studio uses the Web Services Description Language (WSDL) to create the proxy.

COM Interop, Transaction, Visual Designer Component Builder

Web forms are very similar to traditional HTML forms. The difference is that Web forms are server-based, meaning you create the user elements on the server. The server has complete knowledge of what the interface looks like, what it can do what data it expects, and so on. Web forms pages are divided into two parts: the visual elements and the accompanying UI logic. These two components are completely separate from each other conceptually, and they can be physically located anywhere you want. Typically, both parts are contained within one .aspx file. The System.Web.UI namescape defines classes and interfaces used in constructing nd rendering elements on a Web form. The most important class in the System.Web.UI is the Control class which defines the properties, methods and events that are common in all server controls in the WebForm framework. Another important class in this namespace is Page which is a derivative of the Control Class. All ASP.NET web pages are instances of derivatives of the Page Class. To have an extensible framework, the System.Web.UI namespace also includes the UserControl class which is similar to Page class except that it is mainly used as the base class for user controls.

The GacUtil is a utility tool that comes with visual studio, it is use to deploy an assembly by adding it into the GAC(Global Assembly Cache). Ex: Type at the command line prompt"C:\gacutil /i ASPMyComponent.dll" will install ASPMyComponent into the GAC

ASP programming is based on scripting languages like Jscript or VBScript which evolves around a mixture of scripting and HTML. ASP .net is base on an advance structured compiled language. -ASP .net with visual studio .net provides an advanced application and session state, management, while ASP performs poorly at providing it. -ASP has a poor error handling capability compare to ASP .net which has it much completed and much advanced. -ASP does not have a built-in mechanism for XML while ASP .net comes with a full XML capability support. -ASP .net has a fully distributed data source support which is missing from classic ASP