I have read all the post regarding IE8 and multifile flash uploads and cannot resove the issue.
If i use Flash I get 0 files in the Files array.
I've tried using the SessionBasedUploadStateStoreProvider but that did not fix it.
flash version 10,0,32,18
Everything else works as it's supposed to, single file upload works fine.
Tested it with Google Chrome and IE 7 and it works.
If you configure NeatUpload-1.3.18/dotnet/app as it's own web site locally and visit Demo.aspx within that site, does the MultiFile control work? How about if you copy Demo.aspx and Demo.aspx.cs into your own site?
Copy the contents of NeatUpload-1.3.18/dotnet/app/NeatUpload into your own NeatUpload subfolder, replacing the versions that are there. You might have older versions of some of that stuff (e.g. NeatUpload.js) which might have IE8-specific bugs.
It's permissions, I'll find it. When I do I'll post it here for others.
When I changed permissions on the web site to Anonymous for the whole site, then changed my my MoveTo destination to everyone:change it worked.
Ok, here is the answer to this iisue. If you want to have a secure upload process. i.e. You only want you users to be able to upload/download files based on thier authentication credentials this is what you need to do.
1. Secure the web site, either basic/SSL or windows authentication. 2. Remove authentication from the NeatUpload folder in your application and set it to Anonymous. 3. Grant the everyone group change rights to your NeatUpload_temp folder. 4. On your final destination for you uploaded files you need to give the local ASPNET account change rights. This is the account under which the moveto method moves the files.
Why this is different than the non-flash uploads I don't know. Maybe Dean can shed some light on this one. I am using impersonation to access the files for download so that may be what is used by the standard upload processes.
Your instructions look correct to me, with the possible exception that if you are using impersonation when you call MoveTo() I think you would need to give change rights to the impersonated account.
The reason this is all necessary when doing flash uploads is that flash can't do Windows Authentication. It acts like a completely separate HTTP client. This is a Flash limitation that is not NeatUpload-specific.