Register
HeaderPane
Main
Hide
Share Link
Print

Upgrading To Version 8.0

Converting an Existing Application

The conversion is not automatic, but takes just a few minutes for a project.

Only a minimal conversion is required when upgrading from SftMask/OCX 7.0 to SftMask/OCX 8.0. SftMask/OCX 8.0 is virtually 100% source compatible with older releases of SftMask/OCX. Your application(s) must be recompiled to use SftMask/OCX 8.0.

Make sure to back up your current projects, before converting your projects. Please read the conversion process specific to your language carefully BEFORE converting your project. After converting, once the control saves updated property settings, you will not be able to return to SftMask/OCX 7.0.

.NET (Managed Languages)
Visual C++ (Unmanaged C/C++)
HTML
Other Development Tools

.NET (Managed Languages)

While most other languages offer a fairly easy conversion, .NET and its languages require a bit more effort, but in most cases it is limited to the steps documented below.

Existing Forms (.cs, .vb Files):

Updating the forms to use SftMask/OCX 8.0 is quite straightforward:

  • A reference to SftMask/OCX 8.0 needs to be added to the project. This is easily accomplished by adding a SftMask/OCX 8.0 control to any form of your project. It is located in the toolbox group Softel vdm, Inc. For information about this, please see "Using SftMask/OCX with .NET". As soon as this new control is added to your form, the references are added to your project. The Solution Explorer window now shows two new references to AxSftMaskLib80 and SftMaskLib80. Once these references are added, the new control can be deleted from your form. The references remain.
  • If you are upgrading from a version prior to 7.0 also perform the following step:
  • Close all forms.
  • Open each form, one at a time, using the View Code menu entry in the Solution Explorer window. The popup menu is accessed by right-clicking on a form name. If you accidentally open a form in design mode, close it without saving, as your current control settings for this form are most likely lost.
    • Edit all occurrences of SftMaskLib70 and replace them with SftMaskLib80. If you are upgrading from a version prior to 7.0, the name reflects that version (for example SftMaskLib65).
    • If you are upgrading from a version prior to 7.0 also perform the following steps:
      • C#: Edit all occurrences of using OLEConvert; and replace them with using Softelvdm.OLEConvert;
      • VB: Edit all occurrences of Imports projectname.OLEConvert and replace them with Imports Softelvdm.OLEConvert
  • The existing references to SftMask/OCX 7.0 (or older) can now be removed. If the Solution Explorer window shows references to AxSftMaskLib70 and SftMaskLib70, these can be removed.
  • If your project includes the source file OLEConvert.cs (C#) or OLEConvert.vb (VB), remove it now. It is no longer needed.

The forms can now be opened and the project uses SftMask/OCX 8.0 exclusively. You will not be able to return to SftMask/OCX 7.0.

Visual C++ (Unmanaged C/C++)

Resource Files

After installing SftMask/OCX 8.0, all your projects will continue to use SftMask/OCX 7.0 until you make the following change in each dialog resource that defines a SftMask/OCX control. Before opening the resource script (RC file), make sure to close the project in Visual C++, then edit the RC file using a text editor and make the following changes:

IDD_MFC_DIALOG DIALOGEX 0, 0, 320, 200
STYLE DS_MODALFRAME | WS_POPUP | WS_VISIBLE | WS_CAPTION | WS_SYSMENU
EXSTYLE WS_EX_APPWINDOW
CAPTION "MFC"
FONT 8, "MS Sans Serif"
BEGIN
 DEFPUSHBUTTON "OK",IDOK,260,7,50,14
 PUSHBUTTON "Cancel",IDCANCEL,260,23,50,14
 CONTROL "",IDC_SFTMASKPHONE,"{{3BB14704-AC40-4737-B5A6-920366D254FE}}",
 WS_TABSTOP,7,33,121,12
END

The ClassID in the CONTROL line describing SftMask/OCX 7.0 should be replaced with the following:

CONTROL "",IDC_SFTMASKPHONE,"{{68AD7894-0187-4683-8951-D9D867DCFDB4}}",

Only change the ClassID (i.e., 3BB14704-AC40-4737-B5A6-920366D254FE), do not change the rest of the line.

You can copy this information directly from this page. The ClassID must be copied as-is, without any modifications.

Once the RC file has been saved, you can open the project in Visual C++ and the project is now using SftMask/OCX 8.0. The controls will save updated property settings, so you will not be able to return to SftMask/OCX 7.0.

Make sure to change ALL occurrences of SftMask/OCX to version 8.0, otherwise you will not be able to open the resource script (RC file).

#import Statements

The #import statement used with SftMask/OCX 7.0 must be replaced with an #import statement for the new version:

Version 7.0:

#import <msdatsrc.tlb> no_namespace

#pragma warning(disable : 4192) // automatically excluding 'Ixxx' while importing type library 'stdole2.tlb'
// For information about the following construct, please see Microsoft's
// KnowledgeBase entry Q224610
#import <SftMask_IX86_U_70.ocx> rename_namespace("SftMaskNameSpace") rename("LoadImage", "LoadImageSftMask")
#if _MSC_VER >= 1400 // need at least Visual Studio 2005
# pragma comment(lib, "comsuppw.lib") // avoid link error in VS2005
#endif
#pragma warning(default : 4192)

using namespace SftMaskNameSpace;

New for SftMask/OCX 8.0:

#import <msdatsrc.tlb> no_namespace

#pragma warning(disable : 4192) // automatically excluding 'Ixxx' while importing type library 'stdole2.tlb'
// For information about the following construct, please see Microsoft's
// KnowledgeBase entry Q224610
#ifdef _WIN64
#import <SftMask_x64_U_80.ocx> rename_namespace("SftMaskNameSpace") rename("LoadImage", "LoadImageSftMask")
#else
#import <SftMask_IX86_U_80.ocx> rename_namespace("SftMaskNameSpace") rename("LoadImage", "LoadImageSftMask")
#endif
#if _MSC_VER >= 1400 // need at least Visual Studio 2005
# pragma comment(lib, "comsuppw.lib") // avoid link error in VS2005
#endif
#pragma warning(default : 4192)

using namespace SftMaskNameSpace;

HTML

SftMask/OCX 8.0 does not include a control for use with Internet Explorer or cabinet files. Web pages that use SftMask/OCX 7.0 (or older) cannot be upgraded to SftMask/OCX 8.0.

Other Development Tools

Most development tools allow access to the ClassID used for controls on a form or dialog. Sometimes this may be accomplished by using a text editor and editing a configuration file, or possibly the development tool allows direct modification of the ClassID.

Generally, the ClassID used for the prior release 3BB14704-AC40-4737-B5A6-920366D254FE must be replaced with the new ClassID 68AD7894-0187-4683-8951-D9D867DCFDB4. Once this step is completed, opening the project is sufficient to allow SftMask/OCX to convert the stored property settings.

For specific instructions or help, please see your development tool's documentation.

Last Updated 11/15/2026 - (email)
 © 2026 Softel vdm, Inc.
Using an AI assistant?Copy the onboarding note and paste it into your assistant. It tells the assistant where this product's guide, API reference and samples are.AI Assistant Onboarding