Q: I don't want a file or folder to be opened on double-click. How do I prevent this?

Implement the BeforeInvokeCommandOnSelected event and in the eventhandler set e.InvocationProcessed = true to intercept the default action. Another option is to implement the FolderChanging event of an attached ShellControlConnector.

Q: How can I retrieve the target of a link when I use the ShellBrowser component?

Use the static method ShellBrowser.GetLinkTarget .

Q: Where can I download older versions (e.g. versions that are still compatible with older operating systems)?

During your maintenance period, they are located at Downloads -> Older versions in the customer area, if you are logged in to your customer account. You should be able to find the installation files and keys of the two last major versions there.

Question 1

I don't want a file or folder to be opened on double-click. How do I prevent this?

Accepted Answer

Implement the BeforeInvokeCommandOnSelected event and in the eventhandler set e.InvocationProcessed = true to intercept the default action.

Another option is to implement the FolderChanging event of an attached ShellControlConnector.

Question 2

The forward/backward buttons in the ShellHistoryToolStrip don't work. What's wrong?

Accepted Answer

Because the history functionality is contained in ShellControlConnector, you need to attach one to the ShellHistoryToolStrip Control by setting the property of the same name.

Question 3

Can I use ShellBrowser.NET Components with Visual Studio Community Edition?

Accepted Answer

Yes. The components can be used with the Community Edition of Visual Studio.

ShellBrowser.NET components are designed for Windows Form, so you need "Windows Desktop" versions/workloads in the Visual Studio Community Edition.

Question 4

How can I retrieve the target of a link when I use the ShellBrowser component?

Accepted Answer

Use the static method ShellBrowser.GetLinkTarget.

Question 5

Can I use the ShellBrowser.NET components in a .NET 8.0 project?

Accepted Answer

Yes; ShellBrowser.NET components are compatible with the .NET 8 target framwork.

Question 6

Where can I download older versions (e.g. versions that are still compatible with older operating systems)?

Accepted Answer

During your maintenance period, they are located at Downloads -> Older versions in the customer area, if you are logged in to your customer account.

You should be able to find the installation files and keys of the two last major versions there.

Question 7

Is cloud storage like OneDrive supported by the ShellBrowser components?

Accepted Answer

Starting with Windows 10 Cloud storage providers can integrate access into Windows File Explorer via shell extensions.

Also ShellBrowser relies on the availability of the needed extensions.

The ExplorerBrowser component matches Windows Explorer very closely offering the same views and columns.

Other ShellBrowser controls such as the ShellListView/TJamShellList are normally able to operate normally with cloud storage views, however some columns might be presented differently (e.g. the synchronization state is presented as textual information rather than an icon).

Question 8

I'm using the ShellChangeNotifier control to monitor directories for changes. Sometimes I only receive FolderUpdate notifications for a folder, instead of explicit events for file creation, removal, etc. What is going wrong?

Accepted Answer

ShellBrowser relies on the Windows notification system to monitor changes. Sometimes individual notifications are summarized into bigger chunks. It depends on the size of the folder, the number of affected elements and also the type of folder whether this happens or not. Unfortunately this behavior cannot be influenced.

Question 9

Which .NET versions / frameworks are supported?

Accepted Answer

A current list of supported frameworks and Windows versions can be found in the compatibility overview.

Question 10

On 03/31/2022 a vulnerability in the Java Spring framework has been found and published, known as Spring4Shell. Is your application affected by this vulnerability and needs to be patched?

Accepted Answer

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.

Knowledgebase

Need further help getting started?