You can also find it under NeatUpload-version
/dotnet/docs/Manual.html in each release.
Frequently Asked Questions
How come the progress bar doesn't display?
Things to check:
- Make sure that the Brettle.Web.NeatUpload.dll is installed in the bin folder of your application.
- Make sure that the top-level directory of your application is actually
configured as a web application, not just a virtual dir.
- Make sure that the UploadHttpModule has been added to the <httpModules> section (or <system.webServer><modules> section if you are using the DefaultAppPool with IIS7) of your Web.config.
- Make sure that you don't have useHttpModule="false" in your Web.config unless you also have useHttpModule="true" in a <location> element whose path attribute corresponds to your upload page. The Web.config for the demo uses
location filtering to restrict NeatUpload's request processing to the Demo.aspx page.
- Make sure that you don't have ASP.NET application-wide tracing enabled for your application. ASP.NET application-wide tracing disables NeatUpload.
If none of those things is the problem, try creating a small test app that demonstrates the problem and attach it to a new issue in the issue tracker.
The progress bar displays, but it doesn't update or it doesn't update consistently. Why?
You might be running a web garden or web farm and need to configure NeatUpload so that all instances of your web app are sharing the same upload state. See the manual for details.
Alternatively, there might be something between the browser and your app that is caching some uploads. For example, the Fortigate device provided by Charter provides anti-virus protection with a default threshold of 10MB. Any file smaller than 10MB would be
virus scanned before hitting the server and thus the progress bar would not update during the first 10MB of the upload.
Why do large uploads fail part way through?
There is probably something between the browser and your app that is limiting the size of the upload. For example,
and IIS7 request filtering have both been known to restrict the size of uploads. To ensure that it isn't a problem with NeatUpload, remove the UploadHttpModule from your Web.config
and try to upload a large file again. You won't get a progress bar, but the InputFile and MultiFile controls should continue to function. If you still get the "page can not be displayed" error when uploading large files, the problem is probably
with something other than NeatUpload. You could create a separate test page on the same server and use a standard FileUpload ASP.NET control (with the UploadHttpModule removed from the Web.config) if you wanted to be absolutely certain that NeatUpload wasn't
the cause. In addition to checking for things like URLScan, you could try uploading from other computers or through other ISPs in hopes of locating the source of the problem.
Why do I get the error "Cannot delete 6f2f01b4f0974f25ab3cbf2d8ff18eab: It is being used by another person or program. Close any programs that might be using the file and try again."?
You have probably accessed the FileContent property of InputFile or UploadedFile and did not close the Stream it returns. This most commonly occurs when you use FileContent.Length instead of just ContentLength.
Why do I get "HttpException - Client disconnected after receiving x of y"?
Don't panic. That could just be a user cancelling an upload or someone's network connection breaking.
Why are filenames cleared on postback?
Browser security restrictions prevent the server from set the names of files to upload.
Is there a way to programmatically set the name of the file to be uploaded?
No. Browser security restrictions prevent that.
My question wasn't answered here. Now what?
Check the manual, especially the Known Issues section. If that doesn't help post in the Discussions forum.