Please check What's New in this version.
PKIBlackbox package has been split to basic and advanced parts. Basic part is included in all packages of SecureBlackbox as BaseBlackbox. Advanced part (PKIBlackbox itself) requires a separate license. It's also included into SecureBlackbox Standard and Professional packages.
The following functionality has been moved to PKIBlackbox (advanced):
SecureBlackbox.PKI.dll has been brought back to the distribution. This assembly includes the above listed functionality. Please update the reference list of your projects and installation packages.
In SecureBlackbox 7.0 we have brought back PKIBBox package with the above listed functionality.
The above listed PKIBlackbox functions are located in BaseBBox.dll, but their use requires a separate license.
Upgrading your project from SecureBlackbox 6 to SecureBlackbox 7 (ActiveX edition)
SecureBlackbox 7 (ActiveX edition) introduces certain changes to the components' declarations. The changes are caused by the need of making it possible for two or more different versions of SecureBlackbox installed on the same machine to work together without conflicts. Shouldn't the declarations have been updated, any SBB6-based product deployed to a client's machine after deployment of your SBB7-based product would override your installation of SBB, leading to incorrect work of your product. However, as SBB7 declarations are completely new and independent from the earlier versions, you may feel confident about the integrity of your product.
We will use "SomeBBox6" and "SomeBBox7" names as substitutions for the real names of all SecureBlackbox libraries. I.e., the phrase "replace all entries of SomeBBox6.dll with SomeBBox7.dll" actually means "replace BaseBBox6.dll, SSLBBoxCli6.dll, SSLBBoxSrv6.dll, SSHBBoxCli6.dll, SFTPBBoxCli6.dll, PGPBBox6.dll with BaseBBox7.dll, SSLBBoxCli7.dll, SSLBBoxSrv7.dll, SSHBBoxCli7.dll, SFTPBBoxCli7.dll, PGPBBox7.dll accordingly".
Visual Basic uses IDispatch interface when dealing with COM components. This means that it accesses components, along with their properties and methods, using their names and not the exact declarations. That's why the only thing that you have to change in most cases is the parameters of the library being referenced. Just do the following for each .vbp, .frm, .cls and .bas file of your project:
The exact changes depend on the method in which COM objects are used in your project. Anyway, all the changes to be introduced to your project are actually a reflection of the changes in the declarations of SBB coclasses and libraries. In particular, the following should be done:
Please feel free to contact us if you are having problems upgrading your project to SBB7.