Brettle Development

• MultiFile allows all users to select multiple files to upload and allows Flash 8+ users to select multiple files from a single file selection dialog.
• ProgressBar displays the upload progress either inline or in a popup.
• UnloadConfirmer prevents users from accidentally interrupting an upload by leaving the page.

Features

• Works in web gardens and web farms.
• Works under medium trust environments when installed in the GAC.
• Works under Mono's XSP/mod_mono and Microsoft's ASP.NET 1.1 or higher.
• Easy to install and use.  Add the UploadHttpModule to the <httpModules> section of your Web.config and drag-and-drop the controls using the Visual Studios Web Forms Designer.
• ProgressBar control can display processing progress in addition to upload progress.
  
• ProgressBar control uses AJAX-style refreshless updates on modern browsers when JavaScript is available, but also allows users without JavaScript to see upload progress.
• Allows customization through styles, custom progress display pages, UploadStorageProviders, and UploadStateStoreProviders, and provides an API for creating your own file upload and progress controls.
• Falls back to using ASP.NET's HttpPostedFile if the NeatUpload UploadHttpModule is not present.  This makes it easy to remove the HttpModule if for some reason it causes problems.
• Streams uploads directly to storage.  This conserves server memory, allows larger uploads, and helps prevent Denial of Service attacks.
• Removes uploaded files when an error occurs.  This helps prevent disk space leakage.
• Licensed under the Lesser General Public License (LGPL), a business-friendly open source license.  See below for details.
  

Demo

Download

svn checkout https://forgesvn1.novell.com/svn/neatupload/trunk

NeatUpload-1.2 users that don't wish to upgrade should download  NeatUpload-1.2.30.zip or NeatUpload-1.2.30.tar.gz.

Documentation

Support

Feedback

Credits

• Joakim Wennergren of Hitone Nordic AB (Sweden) for contributing the SqlServerInputFile extension which streams uploads to an SQL Server database.
• ForeverStor for funding development of the HashedInputFile extension and reporting a long-standing but rare file corruption bug.
• Joe Audette for his support, patience, and encouragement.  Joe tested countless early versions on MS ASP.NET, contributed VS.NET projects/solutions, and created the awesome mojoPortal, for which NeatUpload was originally designed.
• Stefano Straus for contributing bug fixes and code for new features.  Stefano is using NeatUpload in the Tustena CRM system.
• Mike Lockyer for spending a lot of time testing NeatUpload's designer support with Visual Studio.
• Jamie Howell with starnow.com, and Michael Teper with Elanex, Inc., for reporting and testing the fix for a bug which could cause disclosure of sensitive information.
• Amir Setoudeh at printrunner.com for helping diagnose a tricky bug with handling error pages.
• John Myczek with Inter-Tel for reporting a buffering problem when using TransmitFile() and testing the fix.
• Titan Fu for providing an ASP.NET 1.1 testbed, internationalization fixes, and other feedback.
• Michel Roy (roy dot michel at gmail dot com) for reporting several bugs and suggesting fixes and improvements.
• Chris Hynes at Assisted Solutions for SlickUpload, which was the inspiration for NeatUpload.  I didn't copy any of SlickUpload's code, but trying to get SlickUpload to work under XSP and mod_mono helped me better understand the problem and, in the end, develop a rather different solution.
• the developers of Mono for providing an open source .NET-compatible platform on which to develop NeatUpload.  The ability to look through the source code was critical to overcoming the lack of good documentation on how to use some of the darker corners of ASP.NET.
• the developers of log4net for providing such an easy-to-use logging framework.  This was critical because the Mono debugger doesn't yet support debugging web apps.
  
• my wife, Jennifer, and our kids, Julia and Joshua, for letting me have a lot of "peace and quiet" to work on NeatUpload.

License

1. Include a copy of the NeatUpload release zip file you are using.  The zip file includes the source code for NeatUpload.
2. Give prominent notice with each copy of the app (a) that NeatUpload is used in it, and (b) where to find the release zip file you included.  Include the notice wherever your application displays it's copyright information during operation.  So, for example, if your app has an "About" link that displays a page that says something like "(C) 2008, You Company.  All rights reserved..."  Then you would need to add the notice to that page.  If your app doesn't display copyright information, but you provide a user's manual, it is sufficient to clearly provide the notice in the manual.  If you don't provide a manual, putting the notice in a LICENSE-NeatUpload.txt file in a conspicuous place is sufficient.  The idea is that your customers need to be able to find the notice easily if they are looking for copyright information once they are using your app.  The notice could look something like:

1. Avoid introducing dependencies on proprietary code.  For example, do not modify NeatUpload such that it references an assembly in your proprietary app.
2. Add a prominent notice to the files you modify stating that you changed the files and the date of the change.
3. Include the complete source code for the dll or exe, licensed under the terms of the LGPL.  NOTE: Although I certainly appreciate being notified of any modifications, from a license compliance perspective, you are responsible for providing the modified source to your customer.
4. Give prominent notice with each copy of the app (a) that a derivative of NeatUpload is used in it, and (b) where to find the included source code.  Include the notice wherever your application displays it's copyright information during operation.  So, for example, if your app has an "About" link that displays a page that says something like "(C) 2008, You Company.  All rights reserved..."  Then you would need to add the notice to that page.  If your app doesn't display copyright information, but you provide a user's manual, it is sufficient to clearly provide the notice in the manual.  If you don't provide a manual, putting the notice in a LICENSE-NeatUpload.txt file in a conspicuous place is sufficient.  The idea is that your customers need to be able to find the notice easily if they are looking for copyright information once they are using your app.  The notice could look something like this: