Hello,

I generated a txt file, but the user requirement says, that the system must ask the user where he wants to download it.

I generated the file this way

File.WriteAllText(Server.MapPath(EPM.Financiera.RecaudosWeb.Soporte.Configuracion.ContextoSitioRecaudos.RutaArchivosGenerados + DateTime.Now.ToLongDateString() + ".txt"), GenerarArchivo());
         Response.Redirect(EPM.Financiera.RecaudosWeb.Soporte.Configuracion.ContextoSitioRecaudos.RutaArchivosGenerados + "archivo.txt");

But it redirects the browser to the txt file and the user would have to manually go to the browser Save as option,

any idea?

Thanks

Instead of redirecting them directly to the txt file you should redirect them to a httphandler which can TransmitFile() the file accross to the user. This will give them the choice to open or save the file:

• http://blogs.msdn.com/petel/archive/2005/12/01/499189.aspx
  

Hi!

Please check this thread. Its similar to your scenario..

http://forums.asp.net/t/1487999.aspx

Thanks. 

deepthoughts:

Hi!

Please check this thread. Its similar to your scenario..

http://forums.asp.net/t/1487999.aspx

Thanks. 

One thing to remember is that with BinaryWrite() or WriteFile() options you have to load the file completly into memory first.

You don't have to load it all into memory with the TransmitFile() example I suggested.

In this particular example of text files there -probably- isnt much difference in it, however if you were dealing with high traffic or potentially large files you can see that this would become a memory hog and slow down your server.

rtpHarry:

deepthoughts:

Hi!

Please check this thread. Its similar to your scenario..

http://forums.asp.net/t/1487999.aspx

Thanks. 

One thing to remember is that with BinaryWrite() or WriteFile() options you have to load the file completly into memory first.

You don't have to load it all into memory with the TransmitFile() example I suggested.

In this particular example of text files there -probably- isnt much difference in it, however if you were dealing with high traffic or potentially large files you can see that this would become a memory hog and slow down your server.

Agree buddy... I was sort of more interested in showing how the file download dialog would appear rather than in the merits of different file writing methods... anyways thanks for the clarification :-)

:)