Knowledgebase

All of our products are being developed in Delphi or C#. Although we use Log4Net with some of the components, they are safe to use, because the reported vulnerability applies to Log4J only.

None of our applications depend on Log4J or any other Java library and are thus not affected by this vulnerability.

This applies to all versions and editions of our applications (TreeSize, SpaceObServer, SpaceObServer WebAccess, HeavyLoad, SmartPOP2Exchange, Exchange Server Toolbox, SpamAssassin in a Box, SpamAssassin for Windows, SmartCallMonitor, SEPA-Transfer, ServerSentinel, and ShellBrowser). It is recommended to always use the latest available versions though to benefit from the latest patches, improvements, and features.

We provide various sample projects that demonstrate different aspects of usage.

You can download the samples as pre-compiled version under the following links:

ShellBrowser Delphi

ShellBrowser.NET

ShellBrowser WPF

You can find the source code of the examples in the "Samples" or "Examples" subfolder of the ShellBrowser installation directory.

For ShellBrowser.NET and ShellBrowser.WPF sample code is also available at GitHub:

ShellBrowser.NET

ShellBrowser.WPF

You can read out file attributes or shell properties using the ItemIdList. You can retreive values either as variant or converted as display value.

For ShellBrowser Delphi components please check documentation here:

IItemIdList.GetPropertyValue

IItemIdList.GetShellInformation

For ShellBrowser.NET Components:

ItemIdList.GetPropertyVariantValue

ItemIdList.GetPropertyDisplayValue

ShellBrowser uses PreviewHandlers installed in the system for the preview. Unfortunately not all of them are capable of handling all kinds of high dpi scenarios. This is not an issue of ShellBrowser components.

If you encounter problems like e.g. the display of a pdf file not filling up the whole FilePreview client area or other display problems, please test if the problem has to do with high dpi settings. Scale your primary monitor to 100% and re-login (even if this is not required in newer Windows 10 versions, it still makes a difference).  

Please also check if the same use case works in Windows Explorer.

You can implement the OnNavigating event (ShellBrowser Delphi Components) or NavigationPending event (ShellBrowser .NET or WPF) respectively. Using the event handler's parameters you can check the path and stop the navigation.

Unfortunately Windows doesn't offer an API for this function, so it is indeed not part of ShellBrowser currently. Note, that commands executed via ShellBrowser can be undone in Windows Explorer though.

An ItemIdList is a type derived from the PIDL that is used by the Windows Shell. It fulfills the same functions as a file system path, but is also available for elements that do not have a file system path, such as virtual elements (like e.g. the "This PC" folder) or files that reside on an attached mobile phone.

You can easily create ItemIdLists from a file system path using the respective constructors.

Getting the path from an ItemIdList can be done using the "Path" or "DisplayPath" properties of an ItemIdList.

Also, whenenver a ShellBrowser component is associated with a path, most likely the ItemIdList can also be accessed via respective "FolderIdList" or "AbsoluteItemIdList" properties (e.g. for ListItems, TreeNodes, etc.).

For further documentation see:

TJamItemIdList (ShellBrowser Delphi components)

ItemIdList (ShellBrowser.NET and ShellBrowser.WPF Components)

You can add the ftp server as "network address" via the context menu of "This PC" (e.g. in Windows Explorer). This will include it as folder and ShellBrowser components will be able to use it the same way as Windows Explorer.

We do not work with activation codes because you can find them very easily on the internet. Typically software manufacturers protect against this problem using online activation, but this would make customer dependent on the availability of our activation servers and an internet connection.
We are working with separate trial and full versions instead, where the full version is not freely available for download and must be installed over the trial version. After purchasing our software, customers get an account for our customer area where they can download the full version for at least 12 months. Our customers will also receive a personalized license key, with which they can install the full version. Login data and key should be stored in a safe place. Installing the full version over the trial version will preserve your existing data and settings.

Most trial/demo versions of our products support the activation with a valid license key and then unlock all the features of the full version.

Alternatively, you can always install the full version over the existing trial version, your settings from the trial version will be taken over unchanged.