Example 1: Adding FileManager control via tagPrefix

Example 1: Adding FileManager control via tagPrefix
Example 2: Adding FileManager control programmatically
Example 3: Advanced features; events, user logic and subfolder permissions

Example 4: Multiple instances on the same page
Example 5: ModalDialog mode and showing/hiding the control via a button click

This example demonstrates adding FileManager control to the page by using <GleamTech:FileManager> tagPrefix:

ASP.NET File Manager

Here is the markup code which renders the control above:

    <GleamTech:FileManager ID="fileManager" runat="server" 
                           Width="800"
                           Height="600" 
                           LicenseKey=""
                           FullViewport="false"
                           UploadMethod="Flash">
 
        <RootFolders>
 
            <GleamTech:FileManagerRootFolder Name="Root Folder 1" 
                                             Path="~/App_Data/RootFolder1" 
                                             Permissions="Full" />
 
            <GleamTech:FileManagerRootFolder Name="Root Folder 2" 
                                             Path="~/App_Data/RootFolder2" 
                                             Permissions="Traverse, List, Download, Upload"
                                             Quota="2000 KB"
                                             AllowedFileTypes="*.jpg; *.gif" />
 
        </RootFolders>
    </GleamTech:FileManager>
 

Descriptions for the control properties:

^Improved ID property is used to specify both the programmatic identifier on the server-side and the javascript variable on the client-side. The javascript variable can be used to access the client-side implementation of the control.
^New Width property is used to specify the width of the control.
^New Height property is used to specify the height of the control.
^New ShowOnLoad property can be set to "false" for hiding the control on load. This is useful when the control will be displayed later on the client-side manually. For example, the control can be displayed via a button's click event.
^New FullViewport property can be set to "true" for resizing the control to fit the browser's viewport (interior of the browser window).
^New ModalDialog property can be set to "true" for displaying the control within a modal dialog which masks the parent element. If FullViewport mode is active then the modal dialog will mask the browser's viewport instead. If omitted, the control will be displayed within its parent element (ie. original location in the DOM tree).
^New ModalDialogTitle property is used to specify the title of the modal dialog.
^New ClientLoaded property is used to specify the client-side event which is raised on load. The value should be a valid JavaScript function name which is accessible on the host page. Function names should be specified without parentheses like "FunctionName" or "Namespace.FunctionName".
^New SortRootFolders property can be set to "false" for displaying the root folders in the original order instead of alphabetically sorted order.
Language property defines the language of the user interface. If the property is set to a specific culture like de-CH (German in Switzerland), the control will first look for the language file de-CH.xml and if the file is not found, it will load the general (fallback) language file of that culture which is de.xml. If omitted, the language file which matches the current culture of the host application will be loaded. If there is no language file which matches the current culture or its fallback, then the default language file en.xml is loaded.
LicenseKey property is for setting the purchased license key to unlock the trial version. If omitted, the control will run in trial mode.
UploadMethod property can be set to Browser, Ajax or Flash. Flash method is the best as it allows you to select multiple files at once in the file selection dialog where Browser and Ajax methods allows you to select only one file at a time. If omitted, Flash method is used by default. Flash method will work in medium-trust level. Ajax method needs higher permissions due to displaying the realtime progress information so it will not be available in medium-trust level. Browser method will allow uploading even in medium-trust level by sacrificing the realtime progress information. Note that there is a fallback mechanism, ie. even if it is set to Flash and if Adobe Flash plugin does not exist in user's browser then the method will be degraded to Ajax or Browser upload automatically so the user will always be able to upload files with a consistent user interface.
MaxZipFileSize property is for limiting the size of the generated zip files on "Add to Zip" and "Download as Zip" actions. It can be set can be set in <Number> KB/MB/GB format (eg. 100 KB or 1 MB or 5 GB). If omitted, there will be no size limit for the zip files.
ShowHiddenFilesAndFolders property can be set to "true" for forcing to show hidden files and folders.
ShowSystemFilesAndFolders property can be set to "true" for forcing to show system files and folders.
ShowFileExtensions property can be set to "true" for forcing to show the extension part of the file names in the file list. When this property is enabled, the extensions will be editable in the prompt dialog boxes (eg. "Rename" and "Add to Zip" actions) too.
ShowSystemTypeDescriptions property can be set to "true" for for forcing to show file and folder type descriptions from the system's registry. If not enabled (default behaviour), then simple (but current language dependant) type descriptions (eg. EXE File) will be shown. Under Medium-Trust, registry access will not be possible so even if this property is enabled, simple type descriptions will be shown.
ShowFoldersPane property can be set to "false" for hiding the folders pane (left pane).

Descriptions for the root folder properties:

Root folders which are to be defined/displayed within the control, are added by using <GleamTech:FileManagerRootFolder> tagPrefix inside the sub tag of the control <RootFolders>.

Name property should be set to the display name of the root folder. This property is required and can not be omitted.
Path property should be set to the actual path of the root folder. It can be a virtual (/webfolder/test), application-relative (~/App_Data/RootFolder1), physical (d:\files) or network (\\server\share) path. This property is required and can not be omitted.
Permissions property can be set as predefined values Full (includes all permissions) or ReadOnly (includes only Traverse, List, Download, Copy permissions) or one of (or combination of) Traverse, List, Create, Delete, Rename, Edit, Upload, Download, Compress, Extract, Cut, Copy, Paste permissions. When combining permissions, they should be separated by comma. If omitted, the root folder will be completely inaccessible.
Quota property can be set in <Number> KB/MB/GB format (eg. 100 KB or 1 MB or 5 GB). If omitted, the quota will be unlimited.
AllowedFileTypes property accepts a semi-colon separated list of file extensions (eg. *.doc; *.xls; *.jpg, *.pdf) that are allowed in the root folder. This property restricts all file actions (List, Delete, Rename, Copy, Move, Extract, Compress and Download) along with Upload action. This means only allowed file types will be visible and manageable in the file list. If omitted, any file type (ie. *) is allowed. Note that you can also define the allowed file names and not the extensions only. For instance, you can use * in any part of the filename such as picture*.jpg which matches "picture34.jpg" or "picture 112.jpg" or use it in the extension such as *.jp* which matches "file.jpg", "file.jpe" or "file.jpeg".