Existing customers who have established applications built with Stingray Studio version 10.1 or earlier are not required to migrate. Migrating to the FoundationEx library is optional. Existing applications will continue to work as they previously did. Customers should migrate to the FoundationEx library only if they wish to use Stingray Studio in conjunction with any new features provided in the MFC Feature Pack, such as the RibbonBar.

The features that the FoundationEx library is built upon are included with the Microsoft Visual Studio 2008 compiler when Service Pack 1 or later compilers are installed.

The FoundationEx library was included in Stingray Studio 10.2 as a preview. Upgrades have been made with each successive versions. Please review this product’s Readme.html file for details.

The files for the FoundationEx library are located in the following structure within the Stingray Studio installation directory:

The libraries are named similarly to the following where [Version] is the current version:

Stingray Lib MFC Lib Release: sflex[Version].lib

Stingray Lib MFC DLL Release: sflex[Version]a.lib

Stingray Lib MFC DLL Debug: sflex[Version]ad.lib

Stingray DLL MFC DLL Release: sflex[Version]as.dll

Stingray DLL MFC DLL Debug: sflex[Version]asd.dll

Stingray DLL MFC DLL Unicode Release: sflex[Version]asu.dll

Stingray DLL MFC DLL Unicode Debug: sflex[Version]asud.dll

Stingray Lib MFC DLL Unicode Release: sflex[Version]au.lib

Stingray Lib MFC DLL Unicode Debug: sflex[Version]aud.lib

Stingray Lib MFC Lib Debug: sflex[Version]d.lib

Stingray Lib MFC Lib Unicode Release: sflex[Version]u.lib

Stingray Lib MFC Lib Unicode Debug: sflex[Version]ud.lib

Refer to the FoundationEx.h section for information on how these static and dynamic libraries are linked to an application.

Stingray Studio includes a file called SupportedPlatforms.h that determines whether the items you are building are supported or not. Include SupportedPlatforms.h in the application’s stdafx.h header file. The file is located in the <StingrayInstallDir>\Include directory.

Stingray Studio includes a file called ManifestDefs.h that facilitates proper generation of manifest files in the application. Include ManifestDefs.h in the application’s stdafx.h header file. The file is located in the <StingrayInstallDir>\Include directory. This should replace any MFC, CRT, or Windows Common Control manifest definitions.

To have access to the functionality in the FoundationEx library, include FoundationEx.h to your application’s stdafx.h file below any necessary Windows include files. The FoundationEx.h header file is located in the <StingrayInstallDir>\Include\FoundationEx directory. This file includes the necessary header files for other functionality in the library, as well as the necessary defines for linking to the libraries.

To have access to the functionality of FoundationEx resources, such as menu ID’s and default toolbar images, include SFLResEx.h in your application. The SFLResEx.h header file is located in the <StingrayInstallDir>\Include\Res directory. To add the header files to a sample or application, open the Resource View and right click on the sample or application’s .rc file and select ‘Resource Includes’.

For some Stingray configurations, you may need to add afxribbon.rc to your resource includes to avoid any errors when compiling. Adding afxribbon.rc to your application may cause conflicts with some LIB Release configurations. To add the file, open the Resource View, right click on your project .rc resource file and select ‘Resource Includes’. Then add the following to the bottom section.

If this is not added, the sample or application will crash on statically linked build configurations.

Include _SFLEXDLL in the preprocessor macros if you want to link FoundationEx as a Dynamic Link Library. Include _SFLEXDLL in the C++ preprocessor settings or define _SFLEXDLL in your stdafx.h header file before including any other Stingray Studio headers.