Hello and welcome to our Knowledge Base. Our experts provide answers to the most frequently asked questions of our customers. Start your information search here to find your answer quickly and easily.
Please enter your query or select one of the above categories.
Knowledge Base ShellBrowser .NET Components
|All entries (Page 1 / 3)|
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.
- Create a new folder to your project, e.g. "ShellBrowser"
- Create subfolders: CommonControls, Controls, Core, Resources and Design
- From the "Source" subfolder of the ShellBrowser.NET installation directory, add all source files (and resources) to the respective folders
- In addition, add the Resources.Designer.cs and Resources.resx from the "Source" subfolder
- Remove references to ShellBrowser.dll and ShellBrowser.Core.dll from your project
You do not need to install ShellBrowser.NET on the build server.
Instead, you can add the ShellBrowser assemblies (ShellBrowser.dll and ShellBrowser.Core.dll) as files to your project and replace the assemblies in the project references by the copied dlls.
Make sure to deploy the ShellBrowser dlls to the build server with your project.
This also gives you full control when updating ShellBrowser.NET to a new version.
Depending on .NET Framework and Visual Studio version the Visual Studio hosting process might interfere with certain registered PreviewHandlers.
This behavior will not occur if Visual Studio is either not running or the hosting process is not enabled.
Try running your project with Visual Studio completely closed, or disable the hosting process in Visual Studio (In "Project\Properties\Debug" uncheck the option "Enable the Visual Studio hosting process".
Make sure that your application has visual styles enabled. You can do this by calling Application.EnabledVisualStyles() or by adjusting your application manifest.
Assign the PathChanged event for a ShellList and the BeforeSelect event for a ShellTreeView. If only want to allow the Windows folder, the code could look like this:
private const string cAllowedPath = "C:\\Windows";
private void shellListView1_PathChanged(object sender, EventArgs e)
// Note: PathCollection also can check if the new Path is a subpath, by calling PathCollection.IsSubPathOf(string, string)
if (!Jam.Shell.PathCollection.SamePath(shellListView1.Path, cAllowedPath))
shellListView1.Path = cAllowedPath;
private void shellTreeView1_BeforeSelect(object sender, TreeViewCancelEventArgs e)
e.Cancel = true;
The .NET Framework has security features enabled by default which permit to open libraries or programs from a network share.
If you like to use programs or libraries from a network share you need to set the permissions accordingly. For a developer system it would be ok to set the "Permission Set" of My Computer/Runtime Security Policy/Machine/Code Groups/All_Code/LocalIntranet_Zone in the .NET Framework Configuration to "FullTrust".
To set up a correct security profile otherwise, please consult a system administrator if you plan to deploy your application to network drives.
Note that this only applies to .NET versions below 4.0, as the security model in .NET 4.0 has been significantly changed. See http://msdn.microsoft.com/en-us/library/vstudio/dd233103%28v=vs.100%29.aspx for details.
The file is necessary to develop software with the ShellBrowser controls but not to run them. "JamDesign.dll" must not be delivered together with the software that is using the ShellBrowser controls.