C#操作Excel后文件不可编辑求助：多点点用法排查

Hey there! The reason your Excel file stays locked for editing is because you're not properly releasing all COM objects created by your code, and there are implicit object creations from chained (dot) syntax that leave Excel processes running in the background. Let's break down the issues and fix your code step by step.

Where the Problem Lies #

Your code has a few spots that leave COM objects unmanaged:

• You're using chained syntax like worksheet.Cells[1, 1] which creates two implicit COM objects (the Cells collection and the target Range object) without releasing them.
• You never close the main Excel.Application instance, which keeps the Excel process alive even after you close the workbook.
• You only release the Workbook but not the Worksheet, Range, or Application objects.

Modified Code with Proper Cleanup #

Here's the corrected version where every COM object is explicitly declared and released:

string excelFinalPath = @"C:\Users\fra31\source\repos\Key Visor\Key Visor\Foglio1.xls";
Microsoft.Office.Interop.Excel.Application application = null;
Workbook workBook = null;
Worksheet worksheet = null;
Microsoft.Office.Interop.Excel.Range cellRange = null;

try
{
    application = new Microsoft.Office.Interop.Excel.Application();
    workBook = application.Workbooks.Open(excelFinalPath);
    worksheet = workBook.Worksheets[1];
    cellRange = worksheet.Cells[1, 1] as Microsoft.Office.Interop.Excel.Range;
    
    if (cellRange.Value != null)
    {
        MessageBox.Show(cellRange.Value.ToString());
    }
    else
    {
        MessageBox.Show("Cell is empty!");
    }
}
catch (Exception ex)
{
    MessageBox.Show($"Error: {ex.Message}");
}
finally
{
    // Close and release all COM objects in reverse order of creation
    if (cellRange != null)
    {
        Marshal.ReleaseComObject(cellRange);
    }
    if (worksheet != null)
    {
        Marshal.ReleaseComObject(worksheet);
    }
    if (workBook != null)
    {
        workBook.Close(true, excelFinalPath, null);
        Marshal.ReleaseComObject(workBook);
    }
    if (application != null)
    {
        application.Quit();
        Marshal.ReleaseComObject(application);
    }
}

Key Changes Made: #

• Explicit object declarations: Every COM object (Application, Workbook, Worksheet, Range) is declared separately, so we can track and release each one.
• Try/finally block: Ensures cleanup runs even if an error occurs during execution.
• Reverse-order cleanup: Release objects starting from the smallest (like Range) up to the main Application—this matches how COM objects are nested.
• Quit the Excel application: This forces the background Excel process to shut down, which was the root cause of your file being locked.

After running this code, your Excel file should no longer be locked for editing.

内容的提问来源于stack exchange，提问作者Francesco Zappalà