EDN Admin
Well-known member
One of the other threads is talking about operating on Excel instances from VB.Net; which is something Ive done quite a bit of from VBA and VB6. I was totally surprised that there seems to be problems with losing track of the instances and getting
them closed down from .Net. There is a 40+ page thread on this site starting in 2006 and a lot of other threads on other sites.
http://social.msdn.microsoft.com/Forums/en-US/vbinterop/thread/a98b7675-c2d5-4036-bbde-53a3b88a4df5 http://social.msdn.microsoft.com/Forums/en-US/vbinterop/thread/a98b7675-c2d5-4036-bbde-53a3b88a4df5
http://devcity.net/Articles/239/1/article.aspx http://devcity.net/Articles/239/1/article.aspx
I can choke down the info in those threads and dont want to rehash the same things, but it leaves me wondering two things.
1. There have been 2 Framework releases since most of that was written (3.5 and 4). Is there anything new in those releases that make this problem easier to handle or even go away?
2. Is there anything inherently wrong with the kill process method on a single user system? It is not very elegant and I understand it would be pretty dangerous on a server; but on a single user system would it leave memory blocks or other resources
hanging somehow? Wouldnt the Windows clean up the unmanaged memory?
Thanks,
Brian
View the full article
them closed down from .Net. There is a 40+ page thread on this site starting in 2006 and a lot of other threads on other sites.
http://social.msdn.microsoft.com/Forums/en-US/vbinterop/thread/a98b7675-c2d5-4036-bbde-53a3b88a4df5 http://social.msdn.microsoft.com/Forums/en-US/vbinterop/thread/a98b7675-c2d5-4036-bbde-53a3b88a4df5
http://devcity.net/Articles/239/1/article.aspx http://devcity.net/Articles/239/1/article.aspx
I can choke down the info in those threads and dont want to rehash the same things, but it leaves me wondering two things.
1. There have been 2 Framework releases since most of that was written (3.5 and 4). Is there anything new in those releases that make this problem easier to handle or even go away?
2. Is there anything inherently wrong with the kill process method on a single user system? It is not very elegant and I understand it would be pretty dangerous on a server; but on a single user system would it leave memory blocks or other resources
hanging somehow? Wouldnt the Windows clean up the unmanaged memory?
Thanks,
Brian
View the full article