Web Server CleanUp Question

Posted on 2012-03-23
Last Modified: 2012-03-26
This may sound like the dumbest question...but I'm NEW to Web Developement and

I've recently begun creating PDF using iTextSharp and if I write to the server and then use Window.Open to display it after the user does what ever they want with it (save, print, etc.) how do I get rid of it on the server so these files don't keep building up?

I tried to display the PDF using Window.Open and then delete the file on page unload but it appears that it deletes it before displaying it, so how do I know when the user is done with the file so I can remove it from the server?


If I create the file using can I open the file automatically instead of displaying the dialog box that gives the user the option to Open, Save or Cancel?  I wouldn't mind using Response.Write if I could automatically open the file on completion.

Question by:smithmrk
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2

Accepted Solution

gery128 earned 500 total points
ID: 37757058
You can do one thing, once your user request for a file, before generating the file you should loop through the directory (where you save your file) and delete all files using IO namespace. So after that you generate one file which will be deleted on subsequent request from the users. That will make sure you will have only one file at a time on server.

Or if you want directly transfer file to response it can be done (assuming the user has Adobe Reader or any other PDF reader plugin installed on browser) by adding special lines to headers:
see this links:

Author Comment

ID: 37757428
Your first link (Stackoverflow) doesn't work...but let me review the other one and I'll get back to you.


Expert Comment

ID: 37759061

Author Closing Comment

ID: 37767611
Not sure which way I'm going to go, but thanks for the advice!


Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this Article, I will provide a few tips in problem and solution manner. Opening an ASPX page in Visual studio 2003 is very slow. To make it fast, please do follow below steps:   Open the Solution/Project. Right click the ASPX file to b…
IntroductionWhile developing web applications, a single page might contain many regions and each region might contain many number of controls with the capability to perform  postback. Many times you might need to perform some action on an ASP.NET po…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question