Is it possible to cast COM object to the custom interface?

Dan Griffin shows the extensibility of Visual Studio 2005 Team Edition for Software Testers by discussing the modification of the existing Test Interface Provider sample in the latest Visual Studio SDK and implements Fuzz Testing.

Dan Griffin

MSDN Magazine November 2007

The .NET Framework can use contexts as an object's execution scope and intercept calls going to and from the object, similar to the way COM+ provides component services. What is new with this mechanism is that the runtime allows developers to take part in the interception chain and add powerful services, thus extending existing component services. This in turn decouples the business logic from the system plumbing and simplifies long-term maintenance. Presently, .NET contexts and interception are undocumented aspects of .NET. This article presents the underlying interception architecture and message processing, explains custom context attributes, and walks through a custom interception-based component service.

Juval Lowy

MSDN Magazine March 2003

Dino Esposito

MSDN Magazine November 2000

A flexible, customizable grid for displaying data is a useful tool for ASP developers. It allows Web visitors to customize their view of your data. This article takes the data grid presented in "Ad Hoc Web Reporting with ADO 2.0" by John Papa and Charles Caison (MIND, December 1998) and adds handy features such as a finds feature that supports multiple finds and a mode for adding and editing records. This version also improves response time by allowing asynchronous record download and it componentizes the code so it can be used as a standalone VBScript class object that can be reused in other pages.

Randall Kindig

MSDN Magazine July 2000

Hello,
 Why am I getting this error on line:

               sp.Price = Convert.ToDecimal(collection.GetValue("Price"));

sp is :
  SPecials_Templates sp = new SPecials_Templates();

SPecials_Templates Defined:

    [MetadataType(typeof(SPecials_TemplatesMetaData))]
    public partial class SPecials_Templates
    {
        public class SPecials_TemplatesMetaData
        {

                [ScaffoldColumn(false)]
            public object Key { get; set; }
            [StringLength(50)]
            public object Template_Name { get; set; }
            [StringLength(12)]
            public object Headline { get; set; }
            [StringLength(12)]
    &nbs

We recently migrated our document management system to SharePoint (WSS 3.0) and I adapted my VB6 client application to search for and retrieve a list of documents from this new SharePoint library using the Lists web service. Although the total number of documents in this library is 90,000 at one site and over 145,000 at another, my VB6 application never retrieves more than 600-700 documents at a time. From reading white papers such as "Working with Large Lists in Office SharePoint Server 2007" (http://go.microsoft.com/fwlink/?LinkId=95450&clcid=0x409), it appears that if my custom user interface limits the number of items returned in a search of these large lists, that it may not be necessary to put these documents into folders. However, our current scanning software, KnowledgeLake Capture, by default places newly scanned documents into folders based on the year, month, day and hour, which means that these documents are placed in nested folders 4 levels deep.

There are also some 20 metadata fields on these document libraries that allow us to filter these document libraries so that search results will in most cases be limited to a few hundred items.

We acquired new servers (Windows Server 2008 with SQL Server 2008) to host our SharePoint libraries and we are running WSS 3.0 S