Text Control Leaving Behind Large Amount of .tmp Files

[jeff]

Hello,

I'm using TextControl Server Version 12 .NET. We're using the control to generate a large Word document (~24 pages) on our web server via a web service method call. The TextControl seems to use the ASPNET machine account's temp directory located on 'C:\Document and Settings\%machine name%\ASPNET\Local Settings\Temp' to do its work, but leaves those files behind once the code to generate our document completes. In our case, about 25 MB of .tmp files are generated and left behind. After about a week of testing in our QA environment, the temp directory was over 10GB in size and used up all the memory on the C:\ drive.

Is there any way to force the TextControl to clean up after itself? We don't want to manually delete the files in the Temp directory after our process is done since we're not the only application on the server.

Thanks in Advance for the Help!

[Björn Meyer]

Hello

Thanks for your request.

Temporary files are only created when MS Word files are opened. Do you use such files as your templates or similar? These files are deleted after the Dispose() of TX Text Control .NET Server.

[jeff]

Thanks for your reply.

We use two separate TextControl objects during our process, and we call .Dispose() on both of them at the end of our process.

On a related note, we've noticed on occasion that when we attempt to copy new binaries into our web application folder (to update the server code), a sharing violation occurs on a TextControl dll implying that some process still has it loaded even though the code that generates our documents has finished executing. I'm assuming it's because the control isn't being garbage collected properly even though we're calling dispose on it.

Any thoughts?

[Björn Meyer]

Hello

Does this happen everytime you are converting the documents? Or only under special circumstances?