FAQ & Knowledge Base

Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.

Categories: ShellBrowser .NET Components | Show all categories

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

All of our products are being developed in Delphi or C#. Although we use Spring4D(elphi) with some of the components, they are safe to use, because the reported vulnerability applies to Java Spring framework only.

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.

If you use the ShellBrowser NuGet packages, you may need to update the packages that are used in your project.

In Visual Studio please check the NuGet configuration of your project, and make sure to use the newest packages that are installed in "ShellBrowser.NET Packages" or "ShellBrowser.WPF Packages".

Normally the packages should be found in the installation folder of ShellBrowser.NET. The "NugetPackages" subfolder is set up as NuGet repository during installation and is accessible under the name "ShellBrowser.NET Packages" in Visual Studio.

In case the packages are missing please re-run the setup using the "/Log" or "/Log="filename" parameter.

In this case, the output of the cmdlet registering the packages is kept on the screen. Please copy the output and send it back to us, including the log-file that is written during setup.

As ShellBrowser makes use of the preview handlers in the system via a  limited official interface, the previews are unfortunately "as is".

If you are requesting additional features, you mostly have to find a different preview. Especially for pdf several programs providing preview handlers are available.

It seems, that depending on the Windows version, the system's preview handler is not automatically registered.

You can do so manually in the registry, or implement the "OnLoadPreview" event to assign the Preview Handler GUID, e.g. :

if (UpperCase(ExtractFileExt(eventArgs.Path)) = '.EML') then begin
  
eventArgs.PreviewHandlerGuid := TShellPreviewHandlerGuids.Mime;

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.

Using the ShellListView you can add custom columns to add custom content.

Please check the project "Customization" in the examples subfolder of the installation directory for more information.

All entries (Page 5 / 7)