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.

The .NET Framework 3.5 provides the foundation for building connected and appealing applications, productively, on a wide variety of systems from the device to the data center.

Microsoft continues to support developers using the .NET Framework platform by providing support for applications built in previous versions to the 3.5 release, so existing applications built for .NET Framework 2.0 or .NET Framework 3.0 will continue to work.

The .NET Framework 3.5 adds new features in several major technology areas:

• Deep integration of Language Integrated Query (LINQ) and data awareness.
• Support for Web 2.0 AJAX-style applications and services in ASP.NET and WCF.
• Full tooling support for WF, Windows Communication Foundation (WCF), and Windows Presentation Foundation (WPF), including the new workflow-enabled services technology.
• New classes in the base class library (BCL) for the .NET Framework 3.5 address the most common customer requests.

Documentation looks the same.  Use Debug class for debug builds, use Trace class for both debug and release builds.

An object that identifies an enterprise bean. A client can serialize the handle and then later deserialize it to obtain a

reference to the enterprise bean. What is home handle

An object that can be used to obtain a reference to the home interface. A home handle can be serialized and written to stable

storage and deserialized to obtain the reference.

Historic Unix uses Swapping - entire process is transferred to the main memory from the swap device, whereas the Unix System V uses Demand Paging - only the part of the process is moved to the main memory. Historic Unix uses one Swap Device and Unix System V allow multiple Swap Devices.

KJava is an outdated term for J2ME. It comes from an early package of Java software for PalmOS, released at the 2000 JavaOne show. The classes for that release were packaged in the com.sun.kjava package.

Java Specification Request (JSR) is the actual description of proposed and final specifications for the Java platform. JSRs are reviewed by the JCP and the public before a final release of a specification is made.

Cisco Information Online. Online service available to Cisco customers that provides electronic services and online information relating to Cisco products. CIO services include product information, software updates, release notes, technical tips, configuration notes, brochures, and download offerings.

COM is an acronym for Component Object Model. COM is a way of building objects that is independent of any programming language.  Every COM object implements an interface named IUnknown. It contains three methods: -         QueryInterface: Returns a pointer to another interface -         AddRef:  Increments the objects reference count -         Release: Decrements the objects reference count. One of the rules of COM says that given a pointer to an interface a client can call any IUnknown method through that pointer as well as any methods that are specific to that interface. Hence all interfaces must support the three IUnknown methods in addition to their own methods.

GDI is an acronym for Graphics Device Interface. The GDI allows you to draw on your windows. It is a device independent output model in the sense that the graphics code that you write for drawing will work on any video output which has a Windows driver.  In order to avoid one window interfering with another while drawing output on the screen GDI uses a mechanism called as device context to avoid this conflict. So when a window draws on a screen, printer or any other output device, it doesn't output pixels directly on the device. Instead it draws to a logical surface represented by a "device context" (DC). A DC is a data structure that has all information that GDI needs to know.  Before a Windows program draws anything on the screen it acquires a DC handle from the GDI and then passes this handle back to the GDI each time it calls the GDI output function. In MFC a DC encapsulates the GDI functions that a program uses to generate output. MFC's CDC class wraps a Windows device context and the GDI functions into one package. CPaintDC and CClientDC are subclasses of CDC and represent the different types of device contexts that windows applications use. E.g. CDC* pDC = GetDC(); //do some drawing Release (pDC);