EDN Admin
Well-known member
We have an older vb.net application, and just discovered an issue this week.<br/>
The application produces a PDF file for reports, and then we send it over to a windows form containing the web browser control in .net 2010.
We did not want to use the PDF control from adobe, as it has issues when resizing a child form, and did not want to force the user to install adobe. Thus be sending in as the url, the web controller picks whats available on the clients machine.<br/>
The issue is that a provider notified us, that when the user launches the report window, an instance of adobe reader is also started. Makes sense as the reader is being used by the web controller to show the pdf right?
Now when we close the web browser window we have added:
Me.Dispose(True)<br/>
GC.Collect()
However, the instance of adobe opened is not closed and continues to run, and after multiple times, could have the potential of eating resources.<br/>
Besides using a PDF viewer control, anyone have some ideas?
<br/>
View the full article
The application produces a PDF file for reports, and then we send it over to a windows form containing the web browser control in .net 2010.
We did not want to use the PDF control from adobe, as it has issues when resizing a child form, and did not want to force the user to install adobe. Thus be sending in as the url, the web controller picks whats available on the clients machine.<br/>
The issue is that a provider notified us, that when the user launches the report window, an instance of adobe reader is also started. Makes sense as the reader is being used by the web controller to show the pdf right?
Now when we close the web browser window we have added:
Me.Dispose(True)<br/>
GC.Collect()
However, the instance of adobe opened is not closed and continues to run, and after multiple times, could have the potential of eating resources.<br/>
Besides using a PDF viewer control, anyone have some ideas?
<br/>
View the full article
