Folderbrowserdialog Unmasked: Everything You Wanted to Know About the Folder Browser Component From .net Framework

Original Article :http://www.ssware.com/articles/folderbrowserdialog-unmasked-everything-you-wanted-to-know-about-the-folder-browser-component-from-dotnet-framework.htm

Introduction

The FolderBrowserDialog, available as part of the .Net framework, provides a folder browser component for your C# and VB.Net applications. The UI consists of a modal dialog which contains a tree control displaying all the files and folders on the system. The user can then browse and select a folder from the tree. The full path of the selected folder is then returned.

Basic Usage

To display a folder explorer UI to the user, a FolderBrowserDialog instance is created and the ShowDialog method is called. This shows the modal dialog containing the folder browser control (tree) and an OK and Cancel button. If the user selects a folder and clicks the OK button, the ShowDialog method returns DialogResult.OK and the SelectedPath property contains the full path of the selected folder. If the user clicks the Cancel button, the ShowDialog method returns DialogResult.Cancel.

Advanced Usage

The FolderBrowserDialog has some additional features such as limiting the view of the file system that is displayed to the user, pre-selecting a folder when the dialog is first displayed and displaying a button to allow the user to create a new folder.

The RootFolder property can be set to the full path of the folder which is to be displayed as the root of the tree control of the folder browser component. For example, if this property is set to Environment.SpecialFolder.Personal, only folders from the 'My Documents' are displayed in the tree, so the user can only select 'My Documents' or its sub-folders.

Prior to displaying the folder browser control, the SelectedPath property can be set to the full path of a folder causing that folder to be pre-selected in the folder browser tree. For example, when this property is set to "c:", the node corresponding to the c: drive is pre-selected in the tree when the dialog is first displayed.

If the ShowNewFolderButton property is set to true, then, in addition to the folder browser tree control, and the OK and Cancel buttons, the folder browser dialog also displays an additional 'New Folder' button which when clicked, creates a new folder under the currently selected folder.

Limitations

While the folder browser component is a handy way to allow the users to browse and select folders, it suffers from many limitations, some of them preventing the component from being of practical use in applications.

Modal Functionality

The folder browser component of the most obvious drawback is that it is displayed in the form of a modal dialog user interface. Displayed, it will prevent the rest of the application until the user selects a folder. As long as the dialog box is displayed, there is no input (keyboard or mouse click) In addition to occur in the dialog box. The user must input may appear before the caller identification or the Cancel button.

This is a very annoying and limited FolderBrowserDialog function. Users are likely to be irritated, and tired when they interact with a modal dialog box each time they want to explore and select a folder. A non-modal user interface controls can be the application itself is a form or dialog box, which is a more user-friendly display of the same user-friendly way.

No Virtual (Non-file system) folders

The FolderBrowserDialog does not allow the user to select virtual (Non-file system) folders such as the Control Panel or My Computer. It only allows the user to select a file system path such as "c:" or "c:windows".

No Files

The component does not allow the user to select files. This is a major drawback since there are many circumstances where the user may need to select a file while still using the tree UI to browse to that file.

Limited Choice of RootFolder

The root folder of the folder browser control can be only set to one of the 'special folders' defined by Windows such as the 'My Documents' or 'My Computer'. This is a major limitation since this means you cannot set the root folder to a path such as the "d:" drive.

No Check Boxes

The folder explorer tree in the FolderBrowserDialog cannot show check boxes next to nodes. Ability to show multi-state check boxes can be a very handle feature for such a control.

No Filtering

The FolderBrowserDialog has no support for filtering. For example, it is not possible to display only network folders or only shared folders or only folders starting with the string "Documents" or files having a particular extension.

No Custom Controls

When using FolderBrowserDialog, you are only limited to the actual folder tree control manager to identify, cancel, and the New Folder button and description tags. This is a can not add custom control dialog box. This will be useful, in many cases, such as when you want to display thumbnails / preview of the selected file / folder, or any other relevant information.

No Appearance Control

The appearance of the FolderBrowserDialog and its constituent controls cannot be changed. Neither can attributes of individual folders show in the folder explorer control be changed. For example, it is not possible to change the background color of the tree control or to set the font and color of individual nodes/folders in the tree.

No Custom items

The FolderBrowserDialog cannot display external/custom items in the folder explorer tree. For example, it may be necessary to display items from an FTP location in addition to the file system items. This is not possible with the FolderBrowserDialog.

No Lockdown

The FolderBrowserDialog operations can freely Folder. The user can rename the folder, go drag

Beyond The FolderBrowserDialog : The FolderView Control

The Folder View Control brings a Windows Explorer-like folder browser component to your applications complete with AutoUpdate, dragdrop, icons, context menus, non-filesystem items, default key-handling, info tips and rename. It features powerful behavior control and customization functionality takes it miles ahead of Windows Explorer by adding features like filtering, checkboxes, custom items, more than one root node, dragdrop control and customization of default context menus, display names, icons and more tips.

The FolderView control is a UI control which can be dropped right inside your own forms and dialogs. A non-modal file & folder browsing/selection experience right inside your own dialogs and forms is something that users will appreciate and find intuitive and simple.

Additionally, FolderView overcomes all the limitations of the FolderBrowserDialog and provides far greater and advanced features and functionality than the FolderBrowserDialog. The following table is a quick comparison of the FolderView Control with the FolderBrowserDialog.

Drop-In Windows Explorer like folder browser functionality.
FolderView Control : Yes
FolderBrowserDialog : Modal UI. The component cannot be dropped in your own form.

• Complete Windows Explorer functionality include a file/folder browsing listview (similar to Windows Explorer's right-side) and a drive selection control (similar to Windows Explorer's address bar)
  FolderView Control : Yes. As part of Shell MegaPack
  FolderBrowserDialog : No
  
  
  
  
  
• Ability to select virtual (Non-file system) folders
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Ability to specify any and all folders as root.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Ability to show files as well as folders.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Multi-state check boxes
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Filtering capabilities
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Custom controls
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Appearance Control
  FolderView Control : Colors and appearance of the control as a whole and of individual folders/files can be changed.
  FolderBrowserDialog : No.
  
  
  
  
  
• Custom Items
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Prevent renaming, drag-drop, context menus
  FolderView Control : Yes. For all folders or on a per-folder basis.
  FolderBrowserDialog : No
  
  
  
  
  
• Multiple root folders
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Change default display names, icons, overlay icons, infotip, etc
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Simply and easy to use API
  FolderView Control : Yes
  Clumsy, inflexible API
  
  
  
  
  
• Access complete information of a file/folder including its displayname, fullpath, checkstate, selection state and attributes like whether it is a shortcut, shared, hidden, readonly, file and folder.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Prevent display of contextmenus for all folders using a simple property or on a per-folder basis using an event.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Prevent dragdrop for all folders using a simple property or on a per-folder basis using an event.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Allow/disallow renaming for all folders using a simple property or on a per-folder basis using an event.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Allow/disallow selection for all folders using a simple property or on a per-folder basis using an event.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Allow/disallow expanding/collapsing on a per-folder basis using an event.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Change default drag actions during dragdrop (e.g. from Copy To Move)
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Control checking/unchecking on a per-folder basis.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Prevent execution of default shell commands ( e.g. Open, Cut, Properties, etc. in response to keystrokes or through the context menu) for all folders using a simple property or on a per-folder basis using an event.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Show/hide hidden folders using a simple property.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Show/hide virtual folders ( e.g. Control Panel ) using a simple property.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Enumerate all folders shown in FolderView.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Enumerate all folders according to folder hierarchy structure.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Execute shell commands ( e.g. Cut, Delete, etc ) on folders.
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  
• Associate developer defined data with each folder
  FolderView Control : Yes
  FolderBrowserDialog : No
  
  
  
  
  

The FolderView control (and Shell MegaPack ) is available in two editions :

.Net Edition : For use in .Net development using Windows Forms, WPF and ASP.Net

ActiveX Edition : For use in applications developed using Visual C++/MFC/ATL, Visual Basic 6, VBA (Access, Word, Excel, AutoCAD,etc), Borland Delphi and Borland Builder, and HTML/ASP pages.

Posted in: asp.net| Tags: Introduction Component article framework everything browser folder unmasked original folderbrowserdialog

---

Do you want to add functionality to convert HTML to PDF to your dynamic ASP.Net Application?

DuoDimension software provides PDF component duo. Net 2.2 that helps you to convert HTML to PDF, your dynamic ASP.Net application.

The new version of PDF-Duo. NET component presented by DuoDimension software developer is a professional server-based component based on ASP.NET allows you to convert HTML to PDF. The component is really appropriate for Web applications

The component can be used in any ASP.NET languages (VB.Net, C# etc.) PDF Duo .Net has C# classes with easy-to-operate methods to convert HTML to PDF as a file or as a stream. So developer after conversion of HTML to PDF can write resulting PDF to the window of Internet Browser directly.

PDF Duo .Net component Key Features:

1. Conversion directions: HTML to PDF, XHTML to PDF, TXT to PDF.
2. HTML file can include formatting styles CSS those will be correct converted to PDF.
3. Makes the best use of invalid or bad formed HTML file.
4. Strict copying of HTML file formatting to PDF file in your own ASP.NET project.
5. Allows to convert either from HTML file or from HTML string stream.
6. Takes a Web Site URL instead of HTML file in order to convert to PDF.
7. Not require the installation, Microsoft Office (R) and is, Adobe Acrobat (R) for support. NET 2.0,. NET 3.0 to. NET 3.5 in

Quality of Converting HTML to PDF

PDF format duo. NET components clever conversion tables, style, graphics, images, hyperlinks, fonts, HTML to PDF, etc.

PDF format duo. NET component to help convert HTML report, HTML file, your application's HTML formatted text to PDF solid copy. This is a very fast to use components written in any ASP.NET Web or Windows applications, can be converted into one or a group of PDF format, HTML / XHTML to PDF files.

The component of HTML to PDF converting is very easy to use and is provided with 2 fully featured demos written in both C# and Visual Basic. They will help you to create your own ASP.NET web applications.
How to convert HTML to PDF in ASP.NET?
Installing package contains source code of demo program. Simple examples with source code help you using the PDF Duo .Net component to successfully convert HTML to PDF. There are examples with C# and VB source code.

It is really work! Just try it!

For more information about the component please visit the product page:
http://www.duodimension.com/html_pdf_asp.net/component_html_pdf.aspx

If you have any questions or concerns about component, let us know:
support@duodimension.com

Posted in: asp.net| Tags: Software NET Application Component asp html functionality pdf duo duodimension

---

Php Frameworks

PHP is a framework, PHP is the latest hot topic in the community, a new framework is being released daily. In the framework of the 40 and over, each framework offers different functionality.

I am going to give a quick overview of 3most popular frameworks.

PRADO is a component-based and event-driven programming framework for developing Web applications in PHP 5. PRADO stands for PHP Rapid Application Development Object-oriented.The sole requirement to run PRADO-based applications is a Web server supporting PHP 5.1.0 or higher. You can use it to develop either open source or commerical applications.

Last version has added native support DB and seamless AJAX support to complement a maturing PRADO framework for PHP Web applications serious business. He added many new controls, examples and tutorials.

Web Programming blogs

Web Programming Tutorials and articles

Its features include:

DB access: the cook needs to support a variety of databases to add a single layer 3. They PDO is a data access, Active Record and is based on SQLMap.

Active Controls: These are AJAX-enabled Web controls that make the creation of an AJAX-enabled Web site extremely easy.

Other major new components

Services:

- TSoapService: a service component supporting SOAP requests

- TJsonService: a service component supporting JSON requests

- TFeedService: a service component supporting feed requests

Modules:

- TDbCache: a generic DB cache module that can use any DB driver

- TDbUserManager: a DB-driven user manager module

Controls:

- TOutputCache: a control enabling fragment page caching

- TClientScriptLoader: a control for loading JavaScript libraries

- TXmlTransform: a control performing inline XML transformation

Cake is a rapid development framework used for PHP, most commonly known design patterns like ActiveRecord, Association Data Mapping, Front Controller and MVC. Our primary goal is to establish a structured framework that PHP users at all levels quickly develop robust web applications, without being able to offer loss of flexibility.

Its features include:

Model, View, Controller Architecture

View Helpers for AJAX, Javascript, HTML Forms and more

Built-in Validation

Application Scaffolding

Application and CRUD code generation via Bake

Access Control Lists

Data Sanitization

Security, Session, and Request Handling Components

Flexible View Caching

Seagull is a mature OOP framework for building web, command line and GUI applications. Licensed under BSD, the project allows PHP developers to easily integrate and manage code resources, and build complex applications quickly.

Its features include:

PHP 4/5 compatible

compact core framework with complete modules in package

Model-view-controller pattern

performance conscious design[citation needed]

multiple input and output formats

integrated object-relational mapper for rapid application development

Loosely coupled components, please use the template of your choice, output to multiple devices or CLI engine

caching

localization. Translated into more than 21 world languages.

integrated PEAR libraries

Web Programming Tutorials and articles

Posted in: javascript tutorial| Tags: Programming Component Access service web framework support php ajax-enabled prado

---

Software Component Update in SCOMO-OMA

1    Short Description
Bernard is a device User and very interested in keeping his phone free of viruses.
He is subscribed to “Mobile Security Forces Co.” and this service provider installs always the latest antivirus software upgrades on his phone as soon as they are available. This way Bernard has better protection against malicious mobile device viruses.

2    Actors
o    End User
o    Device
o    Service Provider (Mobile Security Forces Co. in this example)
o    Device Management System

2.1    Actor Specific Issues
o    End User: The End User wants to have the newest release of antivirus software.
o    Service Provider: The Service Provider assigns what software component should be installed by default on a specific Device type. The provider is authorised to define and change the default software on a Device type.
o    Device Management System: The Device Management System issues and handles the commands in the service.

2.2    Actor Specific Benefits
o    End User: End User has good protection against malicious mobile device viruses.
o    Service Provider: The Service Provider is able to deliver the software component updates into the Device.
o    Device Management System: The Device Management System is able to manage the software component in the Device.

3    Pre-conditions
•    Installed software component on a Device is to have added functionality applied or is to be enhanced for security or performance reasons.
•    Device is capable of interfacing with the Device Management system.
•    Security constraints imposed by Device Management System and any DM Client are met.

4    Post-conditions
•    All software component updates targeted at the device have been delivered and installed.
•    Device and all purchased services are fully operational.

5    Normal Flow
1.    The Device Management System issues a request to the Device to install software component updates.
2.    The Device issues a request to the User for authorization to install updates.
3.    Upon confirmation by the User, the Device sends the response to the Device Management System.
4.    The Device Management System initiates software component download and update..
5.    The Device sends a confirmation back to the Device Management System.

6    Alternative Flow 1
1.    The device initiates a session with the Device Management System to request software component update.
2.    The Device Management System has detailed information of the software component available in the device, e.g. whether each software component has been installed/removed, what version the software component is, whether updates should be done promptly or later on.
3.    The Device Management System will selectively issue a request to the Device that has outdated software component version.

7    Alternative Flow II
1.    In the Normal Flow above it turns out that component of antivirus software (that are about to be updated) requires an update of another component (e.g. a special version of Application X).
2.    The Device Management System signals to the device that these components must either be both successfully installed or none of them should.
3.    The Device respects the signal and treats both updates as if they were one. Unless update of both components succeeds – the operation is canceled and an error status is sent back to the server, indicating the problem.

Posted in: Mobile| Tags: Software OMA DM SCOMO Component Actor Condition

---

Software Component Installation in SCOMO-OMA

1    Short Description
Arnold is a device User and very interested in the latest mobile applications.
He is subscribed to “Fun Applications Co.” and this service provider installs always the newest applications on his phone as soon as they are available.

2    Actors
o    End User
o    Device
o    Service Provider (Fun Applications Co. in this example)
o    Device Management System

2.1    Actor Specific Issues
o    End User: The End User wants to have the newest applications on his device.
o    Service Provider: The Service Provider assigns what application software should be installed by default on a specific Device type. The provider is authorised to define and change the default software on a Device type.
o    Device ManagementSystem: The Device Management System issues and handles the commands in the service.  Note that the Device Management System can reside under different authorities, such as service provider itself or network operator, depending on the infrastructure.

2.2    Actor Specific Benefits
o    End User: End User is able to use the latest version of services.
o    Device: Device receives the latest software component/s.
o    Service Provider: The Service Provider is able to deliver the software components into the Device.
o    Device ManagementSystem: The Device Management System is able to manage the application in the Device.

3    Pre-conditions
•    Device is capable of interfacing with the Device Management System.
•    Security constraints imposed by Device Management System and the Device are met.

4    Post-conditions
•    The software component targeted at the device has been delivered and installed.
5    Normal Flow
1.    The Service Provider sends via Device Management System a command to the Device to install a software component.
2.    The Device issues a request to the User for authorization to install upgrades.
3.    Upon confirmation by the User, the Device sends the response to the Device Management System.
4.    The Device Management System initiates the software component download, install, and execution.
5.    The Device sends a confirmation back to the Device Management System.

6    Alternative Flow
The device initiates a session with the Device Management System to request software component installation.
The device informs the user of the SW characteristics before download and installation.(price, providers, compatibility, QoS, characteristics...)
The device Management system may interact with an external management authority in order to coordinate the procedures with other software components.

Posted in: Mobile| Tags: OMA DM SCOMO Component Installation Actor

---