Integrating into your Application

Integrating Mediachase FileUploader is easy. All components of Mediachase FileUploader has been designed to minimize integration time into existing applications. It has been used through out our own projects.

Following list defined overall integration principles:

• Support for several integration methods: Simple, Medium and Full
• Easy to switch from one method to another, including totally disabling Mediachase FileUploader
• Controlling Interfaces are intuitive and are similar to system elements
• Controlling elements support styles of standart control elements
• Allow to set page filters
• Full support of server and client validators
• Full support of Design-Time mode

You have added Mediachase FileUploader into your project, the FileUploader works in Simple mode. You can use either HtmlInputFile or McHtmlInputFile controls because these have similar interface.

The FileUploader is moved in Medium Mode if you have registered McHttpModule. Now you can get a progress information from a page with McHtmlInputFile controls.

And final step, you have turned on a large file optimization, the FileUploader works in Full mode. You can not use direct access to HtmlInputFile controls because the FileUploder.NET control replaces a Real File from the memory with the Active Marker and saves file into the Temp folder.

To solve interference with System.Web.UI.HtmlControls.HtmlInputFile problems w e have  implemented  that the McHttpPostedFile can be created from the HttpPostedFile source and added page filters (Page Filter specifies whether to allow or deny the FileUploader.NET for the ASP.NET pages) .

Comparison table of different integration modes:

	Simple	Medium	Full
Mediachase.FileUploader.McHttpModule used	No	Yes	Yes
File upload optimization is on	No	No	Yes
Progress Bar Support	No	Yes	Yes
Ability to use Mediachase.FileUploader.Web.UI.McHtmlInputFile	Yes	Yes	Yes
Ability to use System.Web.UI.HtmlControls.HtmlInputFile	Yes	Yes	No
maximum post request determined early	No	Yes	Yes