String postUrl = " + projKey + "/attachments" String _auth = string.Format("", "Basic", _enc) Var obj = SQLQueries.ParseQuery(false, "select * from form") Return ername = "admin" & this.password = "admin" So, for above, then with UpLoadFiles, then any WEB based path name (url) will be this: So, the folder MUST be in the root, or at the very least start in the root or base folder your project is. So, that will simple create a sub folder in your project, you see it like this: So, you right click on the base project and add, like this: So we right click on the project and choose add-> (and make sure you use VS to add that folder). So, if you have the project folder, you can add a sub folder to that project. And if you published to a real web server, that would be the case. So, in effect, you have to consider your VS web project the root folder. However, web based file (urls) are ONLY ever mapped though the web site.
So, you could up-load a file, and then with code behind save the file to ANY location on your computer. In that case, files are ONLY EVER mapped to the root of your project, and then sub folders. Then we have requests from the web side of things (from a web page, or a URL you type into the web browser.
However, you working on your development computer - you are in a effect a super user, and you (and more important) your code thus as a result can read/write and grab and use ANY file on your computer.Ĭode behind = plane jane windows file operations.
However, in practice when you use a full blown web server running ISS (which you not really doing during development with VS and IIS express)? Often, for reasons of security, then ONLY files in the wwwroot folder is given permissions to the web server. For the most part, that means code behind can grab/use/look at any file on your computer.
For the most part, any code, any file operations using full qualified windows path names. Ok, so you have to keep in mind how file mapping works with IIS.