I'm having the same issue.  Any idea when you will have this issue corrected?

They were able to duplicate this issue, that's why they opened the support ticket.  I assume they will post on this thread when the fix is available.

My workaround is to let the upload save the file in the upload directory and I rename it in the server-side uploadfinished event, then on the clientside onuploadFinished event, I perform a click event on a hidden button to initiate postback that will process the file.  Since I'm renaming the file to ensure that it is unique, I create a cookie (suggested by support) with the file name to attach to the response.  This cookie is then available on the postback and that's how I know what file to use.  This works for now, but I am very disappointed in the implementation.

This is what I would hope for:

1) The upload control is configurable for one single directory to receive uploads.  It should at least allow you to change the directory per control.

2) I'd actually prefer it didn't write my file to a directory, I wish I could handle the upload event and just get the bytes that were uploaded so that I could just take the file in memory and process it as I desire.

3) Once the bug is fixed and I have access to the session and I can process the file on the upload event handler, it would be nice to be able to return a serializable object in a JSON format back to the client so that I can provide information back to my user.  Because even if I can process the file as soon as it uploads, the way it is designed, it seems I'm always forced to make another request to get the messages that are needed to display the results of the operation.

Hi Georgi,

Has this issue been resolved yet? I am running into the same issue with needing to access the HttpContext.Current.Session as well.