Welcome to our Knowledge Base. Search or browse through the topics below to find answers to your questions.
Probably there was no problem with removing the ShellBrowser.NET files.
Instead Visual Studio sometimes has a problem updating the toolbox from the its cache.
To clear the situation, you can just manually delete remaining components form the toolbox via the context menu (> Delete).
In persistent cases you can choose "Reset Toolbox" to force Visual Studio to update the toolbox.
Not all controls in the ShellBrowser WPF Edition are native WPF controls. Some - like ExplorerBrowser - host ActiveX controls, others like currently the ShellTreeView and ShellListView are Windows Form based.
Mixing those components in a WPF app is underlying some technological restrictions that turn up as "airspace problems" (see e.g. https://docs.microsoft.com/en-us/dotnet/framework/wpf/advanced/technology-regions-overview).
Unfortunately, we cannot fix these issues. In future versions of the WPF Components we therefore plan to add more native WPF controls that can be used as a replacement for the Windows Forms based ones.
In case of doubt, please don't hesitate to test the controls intensively using the demo version.
ShellBrowser uses registered preview handler shell extensions for the FilePreview component. Some of these extensions belong to Windows, others are installed with third party applications.
If the FilePreview is not working, please check the following list:
When configuring ExplorerBrowser to only include the FolderView, it looks much like the ShellListView.
ExplorerBrowser wraps a Windows system component, and thus it will look exactly like Windows File Explorer.The ShellListView on the other hand derives a Windows Forms ListView control, that tries to resemble Windows File Explorer as much as possible. While it misses some aspects of this, it can on the other hand be customized more widely visually and functionally.
Current category: ShellBrowser .NET Components