Hi Joe.

Very odd - the web.config has trust level set to "High", but I have tried setting it to "Medium" and it still works.

A quick google said something about network/file permissions - are you using a local/remote IIS or the one build into Visual Studio? Or something about file permissions where the solution is?

It works with the VS build in hosting-thingy (forgot its name) and I have it running on IIS 7.0 in full trust at work and at a hosting provider with my own website (which says it uses medium trust, but is closer to High trust.) But I must admit I have not tried it using the local IIS (my machine is a bit underpowered for that), so maybe it requires some extra settings for that? I just tested the unzipped solution with VS on my work computer, and it runs fine there too (without using IIS).

!?

Edit: Most likely you put the unzipped solution on a network or external drive. Putting it on a local drive should solve it?

Regarding Azure, it is an interesting new platform which I unfortunately have not yet had a reason to study - so thank you for giving me a good reason to study it! :-)

But is Azure not always based on SQL Server? So wouldn't the version of my upload control which stores uploaded files in the database instead of the file system be perfect for that?

Remember, my upload control does not actually try to save any files to any public part of your website - it just holds them and passes them to your server code (in a partial postback event), so you can decide what you want to do with them. And you might as well store them a totally different place than the database or the file system, if you have such a place available. This of course also give you "2 hops", but in each their own postback.

But I could take my session-based version and see how it could store the temporary files in the Azure blob storage instead of the file system - if the normal website structure is available so that my two upload handlers can receive the files?

(Honestly, I have no idea how a website without a file system is structured... And I also got two paid projects I need to finish now, so it will probably take a few weeks before I get back to studying Azure. Sorry.)

Edit: JavaScript in older browsers (like Internet Explorer) can postback to special URLs, but the file content of the postback cannot be manipulated by JavaScript, so it requires a special upload handler to extract the file upload (which can be attached to the postback in two different ways) and store it. For security reasons I would also recommend having an upload handler to accept or reject uploads, as even though Silverlight or Flash could do what you want client side, their actions can be seen and misused by a hacker if there is the slightest hole in the security rules (for example you should not allow reading an uploaded file before your code have verified it is safe, and have removed upload rights so it cannot be replaced).

Bests

Allan K.