Contact Desaware and order today! 

Sign up for Desaware's Newsletter for the latest news and tech tips.

SpyWorks Support

Frequently Asked Questions - .NET Specific

1. I get a run time exception in the InitializeComponent function of a form containing the dwsbc36 Subclass control in Visual Studio 1.1.
2. Which features of SpyWorks are compatible with .NET?
3. What languages will SpyWorks .NET samples be provided in?

The dwsbc36 Subclass ActiveX control will generate a run time System.InvalidOperationException during initialization in Visual Studio .NET version 1.1. This seems to be caused by some sort of incompatibility with the version 1.1 framework. You can add a Try Catch statement to catch this error and ignore it. Look for the following line of code in the form's InitializeComponent function:

[VB] CType(Me.SubClass1, _
System.ComponentModel.ISupportInitialize).EndInit()

[C#] ((System.ComponentModel.ISupportInitialize)
(this.SubClass1)).EndInit();

Modify it to the following:

[VB] Try 
         CType(Me.SubClass1, _
         System.ComponentModel.ISupportInitialize).EndInit() 
         Catch ex As System.InvalidOperationException 
         ' ignore VS 2003 compatibility exception 
     End Try

[C#] try { ((System.ComponentModel.ISupportInitialize) 
           (this.SubClass1)).EndInit();
           } 
     catch (System.InvalidOperationException ex) 
         { // ignore VS 2003 compatibility exception }

Or you can use the new native .NET Desaware.SpyWorksDotNet11.dll assembly (included with SpyWorks Professional 7.1) to do subclassing in version 1.1.

SpyWorks 7.1 includes a native .NET subclassing and hook component. It is also compatible with additional SpyWorks features and components through interop:

As of SpyWorks 7.1, the following have been tested for compatibility with Visual Studio .NET 1.0 and 1.1:

Subclass Control - dwsbc36.ocx. Samples are included demonstrating how to use this control in .NET.

WinHook Control - dwshk36.ocx. Samples are included demonstrating how to use this control in .NET.

SpyWorks Function Library - dwspy36.dll.

• Object access functions no longer applies for .NET objects.
• Note that many of the SpyWorks functions that returns a String data type returns a BSTR which is different than the .NET String Data type - refer to the samples on converting or marshalling the data type.
• The dwGetAddress* functions still works but we recommend that you use .NET framework's platform-invoke functionality to pass references to data types instead.

Dynamic Export Function Libraries

COM based export functions created with the SpyWorks Dynamic Export Technology can be called from .NET without having to change the original source, refer to the samples on how to pass .NET parameters and how to declare the export functions.

.NET samples included with Pro 7.0 demonstrates how to call .NET based export functions from VB 6.

Most .NET samples written in C# and Visual Basic.