Upgrading to Version 3.5
Converting an Existing Application
The conversion is not automatic.
Only a minimal conversion is required when upgrading from SftDirectory 3.0 to SftDirectory 3.5. SftDirectory 3.5 is virtually 100% source compatible with older releases of SftDirectory. Your application(s) must be recompiled to use SftDirectory 3.5.
SftDirectory 3.5 and older versions of SftDirectory can coexist on the same system (both can be installed and used at the same time) and they can be used in the same application.
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 SftDirectory 3.5.
Visual Basic
.NET (Managed Languages)
Visual C++ (Unmanaged C/C++)
Delphi
Other Development Tools
Visual Basic
After installing SftDirectory 3.5, all your projects will continue to use SftDirectory 3.0 until you make the following change in each project's main VBP (Visual Basic Project) file. Before opening the project file, make sure to close the project in Visual Basic, then edit the VBP file using a text editor and make the following changes:
Existing Project File (VPB File):
Type=Exe
Form=Form1.frm
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.5#0#G:\WINNT\System32\stdole2.tlb#OLE Automation
Object={5D4DD600-A491-4f1c-9768-EE878F77EF2E}#3.0#0; SftDirectory_IX86_U_30.ocx
IconForm="Form1"
Startup="Form1"
ExeName32="yourexe.exe"
Command32=""
Name="yourproject" The line describing SftDirectory 3.0 (above, using a bold font) should be replaced with the following:
Type=Exe
Form=Form1.frm
Reference=*\G{00020430-0000-0000-C000-000000000046}#2.0#0#G:\WINNT\System32\stdole2.tlb#OLE Automation
Object={4CFACA80-AA04-421F-97AF-5A46A5F5C697}#3.5#0; SftDirectory_IX86_U_35.ocx
IconForm="Form1"
Startup="Form1"
ExeName32="yourexe.exe"
Command32=""
Name="yourproject" You can copy this line directly from this help file. The line must be copied as-is, without any modifications.
Existing Forms And Modules (FRM, BAS Files):
All forms and modules must be edited using a text editor. The following changes can easily be accomplished by a global edit and replace operation:
All occurrences of "SftDirectoryLib30." must be replaced by "SftDirectoryLib35." (make sure to enter the trailing period for both strings).
Once the VBP file has been saved, you can open the project in Visual Basic and the project is now using SftDirectory 3.5. The controls will save updated property settings, so you will not be able to return to SftDirectory 3.5.
.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 is limited to the steps documented below.
Existing Forms (FRM Files):
Updating the forms to use SftDirectory 3.5 is quite straightforward:
- A reference to SftDirectory 3.5 needs to be added to the project. This is easily accomplished by adding a SftDirectory 3.5 control to any form of your project. Any form (or a new form) that does not already contain a SftDirectory control can be used. For information about this, please see "Using SftDirectory 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 AxSftDirectoryLib35 and SftDirectoryLib35. Once these references are added, the new control can be deleted from your form. The references remain.
- 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 SftDirectory control settings for this form are most likely lost.
- Edit all occurrences of SftDirectoryLib30. and replace them with SftDirectoryLib35. (IMPORTANT: include trailing period for both strings). This implicitly replaces AxSftDirectoryLib30 with AxSftDirectoryLib35.
- The existing references to SftDirectory 3.0 can now be removed. If the Solution Explorer window shows two references to AxSftDirectoryLib30 and SftDirectoryLib30, 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.
- Add the SftHelperComponent component to any form of your project. It is located in the toolbox group Softel vdm, Inc. For information about this, please see "Using SftDirectory with .NET". It eliminates the need for the OLEConvert.cs or OLEConvert.vb source files that were used in earlier releases.
The forms can now be opened and the project uses SftDirectory 3.5 exclusively. You will not be able to return to SftDirectory 3.5.
Visual C++ (Unmanaged C/C++)
Resource Files
After installing SftDirectory 3.5, all your projects will continue to use SftDirectory 3.0 until you make the following change in each dialog resource that defines a SftDirectory 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_SFTDIRECTORY1, "{5D4DD604-A491-4f1c-9768-EE878F77EF2E}",
WS_TABSTOP,7,26,364,180
END The contents of the line describing SftDirectory 3.0 (above, using a bold font) should be replaced with the following line:
CONTROL "",IDC_SFTDIRECTORY1, "{4CFACA84-AA04-421F-97AF-5A46A5F5C697}", Only change the ClassID (i.e., 5D4DD604-A491-4f1c-9768-EE878F77EF2E to 4CFACA84-AA04-421F-97AF-5A46A5F5C697), do not change the rest of the line.
You can copy this information directly from this help file. The ClassID must be copied as-is, without any modifications.
Make sure to change ALL occurrences of SftDirectory to version 3.0, otherwise you will not be able to open the resource script (RC file).
Once the RC file has been saved, you can open the project in Visual C++ and the project is now using SftDirectory 3.5. The controls will save updated property settings, so you will not be able to return to SftDirectory 3.5.
#import Statements
Any #import statements that are used in your application must now use the new control:
#pragma warning(disable : 4192) // automatically excluding 'Ixxx'
// while importing type library
#import <SftDirectory_IX86_U_30.ocx> rename_namespace("SftDirectoryNameSpace") \
exclude("_STRRET") exclude("UINT_PTR") exclude("tagOleMenuGroupWidths") \
exclude("FOLDERSETTINGS") exclude("IShellFolder") exclude("IEnumIDList") \
exclude("IShellView") exclude("IShellBrowser")
#pragma warning(default : 4192)
using namespace SftDirectoryNameSpace; should be replaced with
#pragma warning(disable : 4192) // automatically excluding 'Ixxx'
// while importing type library
#import <SftDirectory_IX86_U_35.ocx> rename_namespace("SftDirectoryNameSpace") \
exclude("_STRRET") exclude("UINT_PTR") exclude("tagOleMenuGroupWidths") \
exclude("FOLDERSETTINGS") exclude("IShellFolder") exclude("IEnumIDList") \
exclude("IShellView") exclude("IShellBrowser")
#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 SftDirectoryNameSpace;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 5D4DD600-A491-4f1c-9768-EE878F77EF2E must be replaced with the new ClassID 4CFACA80-AA04-421F-97AF-5A46A5F5C697. Once this step is completed, opening the project is sufficient to allow SftDirectory to convert the stored property settings.
For specific instructions or help, please see your development tool's documentation.
On
Off