Client-Side File Explorer
-
I am creating a webpage in ASP.NET 2.0 where a client can browse through their hard drive in an explorer-like treeview control and select the files they want to upload, but how can I populate the treeview control with the client's hard drive and not the server's?
-
I am creating a webpage in ASP.NET 2.0 where a client can browse through their hard drive in an explorer-like treeview control and select the files they want to upload, but how can I populate the treeview control with the client's hard drive and not the server's?
-
I am creating a webpage in ASP.NET 2.0 where a client can browse through their hard drive in an explorer-like treeview control and select the files they want to upload, but how can I populate the treeview control with the client's hard drive and not the server's?
-
the HtmlInputFile control already does that. 1 line of code equals many bugs. So don't write any!!
thx for the advice guys, I'm using javascript to populate the treeview by a combination of the Scripting object Script.FileSystemObject and .net 2.0 callback events, but I get a "Automation server can't create object" error when I run the site. It throws that error when I try to instantiate the following, "var fos = new ActiveXObject('Scripting.FileSystemObject');". I googled this error and almost everyone says to upgrade Windows Scripting, which I did to version 5.6, but I still get the error. Weird thing is that if I run the page locally I get no errors and it works, but if I run the page under my IIS I get this error, so is there a way I can update windows scripting under my IIS or is there an alternative solution to this?
-
thx for the advice guys, I'm using javascript to populate the treeview by a combination of the Scripting object Script.FileSystemObject and .net 2.0 callback events, but I get a "Automation server can't create object" error when I run the site. It throws that error when I try to instantiate the following, "var fos = new ActiveXObject('Scripting.FileSystemObject');". I googled this error and almost everyone says to upgrade Windows Scripting, which I did to version 5.6, but I still get the error. Weird thing is that if I run the page locally I get no errors and it works, but if I run the page under my IIS I get this error, so is there a way I can update windows scripting under my IIS or is there an alternative solution to this?