09 Jan 2005
28 Dec 2010
Link to this post
Yes, this is a show-stopper for my migration plans too.
My 3.7 sites all use filesystem storage, for all of the reasons mentioned (and a problem with uploading large blobs in 3.7) so I can't consider migrating until this 3.7 feature is implemented.
However, the 3.7 implementation could do with some improvements, and the ones mentioned ring a bell with me.
While not directly linked, I also have problems with customers wanting to upload very large files (the reason for using filesystem storage) using ADSL connections, which creates all of the expected timeout issues.
In 3.7 this requires messing about changing the defaults for executionTimeout and sessionState timeout , which is something I'm always reluctant to do, for possible security issues.
It would be good if V4 could eliminate the need to mess about with the ASP.NET defaults by providing settings to be applied programmatically at run-time to the upload process.
Also, it would be nice if the upload utilities could access files from admin specified locations on the server, so that a separate FTP option could be used for the upload grunt-work, and then the files imported once uploaded.