Bug? Add a table

[lavoratoreAcottimo]

In versions higher than 1.0.10 when I try to add a table with
document.AddTable(2, 2);
as shown in the example, I get an error:

Object reference not set to an instance of an object.
at OfficeIMO.Word.WordTable.get_Rows()

Version 1.0.10 seems to work.

Thanks

[PrzemyslawKlys]

Thanks for reporting this, and for checking against 1.0.10.

I tried to reproduce the issue locally with the same minimal call:

document.AddTable(2, 2);

and I wasn’t able to reproduce it. I tested it with 1.0.10, 1.0.41, and current source, and in each case the table was created successfully.

So at the moment this does not look like a general AddTable() regression, but your stack trace is specific enough that there may still be an environment- or setup-specific issue involved.

If you can, please share:

• the exact OfficeIMO.Word version
• the target framework (net472, net8.0, etc.)
• the full stack trace
• a minimal repro project

It would also be worth trying a clean rebuild:

• delete bin / obj
• restore packages again
• rebuild from scratch

Since the same call works in a clean repro here, this may be caused by a package/cache mismatch or a different runtime setup rather than AddTable() being broken in all versions after 1.0.10.

[lavoratoreAcottimo]

Thanks for your suggestion.
I found that if I run in the Debugger the error comes up. If I run without the debugger everything is OK.
I checked your code and I think that you added RefreshTblGridFromColumnWidths. Here there is a try catch that when I run in the debugger is not "honored" and therefore the _table variable is set to null, causing the error.

Thanks again

[PrzemyslawKlys]

Thanks, that was very helpful.

You were right to point at RefreshTblGridFromColumnWidths(). I checked the flow more closely and the problem is that the grid refresh was being called during table generation, before _table had been assigned on the WordTable instance.

So what happens is:

• without the debugger, the exception is handled and execution continues
• with the debugger attached, Visual Studio can stop on that handled first-chance exception, which makes it look like AddTable() is failing

So the catch is not really being ignored, but the debugger is surfacing the exception before normal flow continues.

I’ve adjusted this so the grid refresh happens only after _table is initialized, which should remove the debugger-only NullReferenceException while keeping the tblGrid refresh logic in place.

Thanks again for taking the time to narrow it down.

[PrzemyslawKlys]

Fixed in:

• Fix debugger exception during table creation #1758