download file to client machine

[Nimesh]

Hi All,

I am new to ASP.NET. I need to download a file from server to the client
machine.

Any ideas on how to go about this ?

Thanks In Advance.

 

[Guest]

hi
make a link to your file and post it on your page.

cheers

 

[Carolina]

You can try something like this:

string FilePath = MapPath("design.doc");
Response.ContentType = "Application/msword";
Response.AppendHeader("content-disposition", "attachment;filename=" + "design.doc");
Response.WriteFile(FilePath);
Response.Flush();
Response.End();

 

[Sriram Krishnan]

If its a static choice, dont do this - as this is really annoying for people
who use download managers - you can't resume the download - and you can't
bookmark the download easily

 

[wolfgang wagner]

You can try something like this:

string FilePath = MapPath("design.doc");
Response.ContentType = "Application/msword";
Response.AppendHeader("content-disposition", "attachment;filename=" + "design.doc");
Response.WriteFile(FilePath);
Response.Flush();
Response.End();

i do have the same problem. but how does this work for files located on
another machine??
this does not work:


string FilePath = MapPath("file.log");
Response.ContentType = "text/plain";
Response.AppendHeader("content-disposition", "attachment;filename=" +
"http://domain.com/file.log");
Response.WriteFile(FilePath);
Response.Flush();
Response.End();

is there a way to get this working too??

greets
wolfgang

 

[Hans Kesting]

i do have the same problem. but how does this work for files located
on another machine??
this does not work:


string FilePath = MapPath("file.log");
Response.ContentType = "text/plain";
Response.AppendHeader("content-disposition", "attachment;filename=" +
"http://domain.com/file.log");
Response.WriteFile(FilePath);
Response.Flush();
Response.End();

is there a way to get this working too??

greets
wolfgang

The AppendHeader line does two things:
- "attachment": makes the "save-box" pop up
- "filename": *suggests* a filename to use on the client-side
It does NOT specify the place to download the file from.

The WriteFile line places the server-file in the response-stream.
It might be possible to use UNC paths to point to a different
server in the local network (local as seen from the server!).
I don't think it is possible to point to a different webserver.
You might want to redirect instead! (also saves some network
traffic: why first get the file from the other server to your server
only to send it out again to the client?)

Hans Kesting

 

[wolfgang wagner]

The AppendHeader line does two things:
- "attachment": makes the "save-box" pop up
- "filename": *suggests* a filename to use on the client-side
It does NOT specify the place to download the file from.

The WriteFile line places the server-file in the response-stream.
It might be possible to use UNC paths to point to a different
server in the local network (local as seen from the server!).
I don't think it is possible to point to a different webserver.
You might want to redirect instead! (also saves some network
traffic: why first get the file from the other server to your server
only to send it out again to the client?)

Hans Kesting

the problem is the location of the downloadable file. i've got a
download script which should "send" the corresponding file (one in
accessible only from internet, the other only from intranet) to the user
depending on his location (internet or intranet) and also insert some
data into a database.

wolfgang