SftTree/OCX 6.0 Support

We are currently shipping SftTree/OCX 6.03.

Hotfixes
Frequently Asked Questions
Useful Topics
Development Tools
Update History
Scheduled Product Updates
In The Works

Please log in to access hotfixes for this product.

Demo Has Expired
UNICODE Support
Rebooting Vista During Installation

.NET, Event Handlers & Debugging
.NET & Dynamically Created Controls
DynamicHelp - Visual Studio 2005/2008
Marshaler Warnings - Visual Studio 2005/2008
Converting from VB6 to VB.NET
About InterDev 6.0 and Windows XP SP2
About Visual FoxPro

Version 6.03:

• Enhancement: Preliminary support for Windows 7.
• VB6 Only: The topic "Upgrading To Version 6.0" had an incorrect Object statement. 

Version 6.02:

• The documentation for Registration-Free Activation (topic "Distributing SftTree/OCX") had an incorrect sample for the manifest file, which caused the control to be registered incorrectly. The < typelib tlbid="... > portion had an incorrect CLSID.

• Enhancement: The web license requirement, when used on web pages, has been removed.

• Visual Studio 2003 only: The OCXHelper control could not be added to a form and would result in error message "The .NET assembly 'Softelvdm.OCXHelper' could not be found".
  Visual Studio 2003 only: Compiling samples would result in error BC30466: Namespace or type 'OLEConvert' for the Imports 'Softelvdm.OLEConvert' cannot be found.
  
  The above problems could be corrected by removing the project reference for Softelvdm.OCXHelper, as it was broken.
  The correct reference could be added to the project's References using the menu command Project, Add Reference..., click "Browse" and locate C:\Program Files\Common Files\Softelvdm\Softelvdm.Controls\Softelvdm.OCXHelper.dll.

• Some of the help file samples were missing.

Version 6.01:

• The OCXHelper control, used for .NET C# and VB development, would not register correctly when used with Visual Studio 2002/2003.
• Debugging a (managed) .NET application under VS 2008 could result in an "OS Loader Lock" message. While just a warning (and not a problem), we redesigned the relevant portion of the control to avoid this warning.

Version 6.00:

• This is the initial release.

The following changes have been implemented and are currently available via hotfix (above) and will be available in the next version.

Version 6.04:

• VB6 only: Compiler can hang if the project setting "Remove information about unused ActiveX Controls" is not selected (Project Settings > Make tab, bottom of the dialog). As a workaround, it is also possible to open the form in design view and keeping it open during compilation.

We are working on the following items, which will be available soon (within a few days to a month).

• None.

Research Only indicates that these items are currently being reviewed to determine an appropriate course of action. No commitment has been made to offer/implement such new features.