![]() |
.NET application does not release Excel
Let me prefix with, I've done many VB6 and ASP applications that read
from/write to Excel and have never had a problem. I'm not a beginner at this... I have created my first .NET Windows application that reads from Excel 2000 and writes to a tab file. I am using the code below and when stepping through the appExcel.Quit() is executed. However, the EXCEL.EXE process still runs and will run until I close the .NET application I've built. This happens in both DEBUG and RELEASE compilations. Try appExcel = New Excel.Application() ... coding tasks ... Catch ex As Exception ... error tasks ... Finally appExcel.Quit() Any ideas why Excel is not being released after the quit? I even tried adding GC.Collect() to see if it helps to force the Garbage Collection to release appExcel. Thanks, in advance. |
.NET application does not release Excel
Try Marshall.ReleaseComObject after quit..
Thanks. "Cameron Eckman" wrote in message ... Let me prefix with, I've done many VB6 and ASP applications that read from/write to Excel and have never had a problem. I'm not a beginner at this... I have created my first .NET Windows application that reads from Excel 2000 and writes to a tab file. I am using the code below and when stepping through the appExcel.Quit() is executed. However, the EXCEL.EXE process still runs and will run until I close the .NET application I've built. This happens in both DEBUG and RELEASE compilations. Try appExcel = New Excel.Application() ... coding tasks ... Catch ex As Exception ... error tasks ... Finally appExcel.Quit() Any ideas why Excel is not being released after the quit? I even tried adding GC.Collect() to see if it helps to force the Garbage Collection to release appExcel. Thanks, in advance. |
.NET application does not release Excel
Because Excel is a COM based application, I'm wondering if you don't need to
manually destroy the Excel object reference like in the COM world: Finally appExcel.Quit() appExcel = Nothing End Try "Cameron Eckman" wrote in message ... Let me prefix with, I've done many VB6 and ASP applications that read from/write to Excel and have never had a problem. I'm not a beginner at this... I have created my first .NET Windows application that reads from Excel 2000 and writes to a tab file. I am using the code below and when stepping through the appExcel.Quit() is executed. However, the EXCEL.EXE process still runs and will run until I close the .NET application I've built. This happens in both DEBUG and RELEASE compilations. Try appExcel = New Excel.Application() ... coding tasks ... Catch ex As Exception ... error tasks ... Finally appExcel.Quit() Any ideas why Excel is not being released after the quit? I even tried adding GC.Collect() to see if it helps to force the Garbage Collection to release appExcel. Thanks, in advance. |
.NET application does not release Excel
"Cameron Eckman" wrote in message
... <snip Any ideas why Excel is not being released after the quit? I even tried adding GC.Collect() to see if it helps to force the Garbage Collection to release appExcel. Thanks, in advance. Knowledge Base Artice: PRB: Office Application Does Not Quit After Automation from Visual Studio .NET Client http://support.microsoft.com/?kbid=317109 Erik |
.NET application does not release Excel
Thanks. I also found the following article:
http://support.microsoft.com/default...b;en-us;317109 I am still having problems, but it seems to do with looping through the cells. I'll have to do ReleaseComObject after I'm done with each cell. What a pain in the.... "Shailesh [MVP]" wrote in message ... Try Marshall.ReleaseComObject after quit.. Thanks. "Cameron Eckman" wrote in message ... Let me prefix with, I've done many VB6 and ASP applications that read from/write to Excel and have never had a problem. I'm not a beginner at this... I have created my first .NET Windows application that reads from Excel 2000 and writes to a tab file. I am using the code below and when stepping through the appExcel.Quit() is executed. However, the EXCEL.EXE process still runs and will run until I close the .NET application I've built. This happens in both DEBUG and RELEASE compilations. Try appExcel = New Excel.Application() ... coding tasks ... Catch ex As Exception ... error tasks ... Finally appExcel.Quit() Any ideas why Excel is not being released after the quit? I even tried adding GC.Collect() to see if it helps to force the Garbage Collection to release appExcel. Thanks, in advance. |
All times are GMT +1. The time now is 12:25 PM. |
Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
ExcelBanter.com