Hi,
I'm having an issue with workbooks property in Excel.
What I'm trying to do is a loop on a same Excel application object:
1. open a workbook
2. read some data
3. close the workbook
4. dispose the workbook
5. loop until there is no file left
But I can see in task manager that Excel memory is growing everytime I loop despite the dispose method. Is there a way to handle this (maybe I'm not using it the right way) or is that a bug?
Comments: ** Comment from web user: SebastianDotNet **
I'm having an issue with workbooks property in Excel.
What I'm trying to do is a loop on a same Excel application object:
1. open a workbook
2. read some data
3. close the workbook
4. dispose the workbook
5. loop until there is no file left
But I can see in task manager that Excel memory is growing everytime I loop despite the dispose method. Is there a way to handle this (maybe I'm not using it the right way) or is that a bug?
Comments: ** Comment from web user: SebastianDotNet **
its difficult to analyze without code example because i did not understand "loop until there is no file left".
(btw: the NO proxy management was safe for all the years)
can i see some code for step 5 ?
nice to know:
in a standalone solution(not sure its yours) you can use the static NetOffice.Core.Default.ProxyCount property and ProxyCountChanged event for diagnostics. it shows you how many proxies currently open in your solution.
Sebastian
