linknet

Inspecting the Microsoft Word plugin code revealed that although most of the hard work to access the com objects etc. had been completed the code to display context lines was unfinished. The intention appears to have been to display context lines based on line and page numbers but the Word Application doesn't really support this. MS Word lines are actually paragraphs (each line word wraps and continues until a carriage return is inserted) and pages are only hard coded if you specifically add page...

I've had another look at this last suggested change and I can't replicate the slow release of the Word Application from memory. At the time of posting I replicated it many times without fail so it's a bit of a mystery! All of the official documentation recommends calling ReleaseComObject for each object in reverse order to their creation, so maybe it shouldn't be removed.

I've had another look at this last suggested change and I can't replicate the slow release of the Word Application from memory. All of the official documentation recommends calling ReleaseComObject for each object in reverse order to their creation, so maybe it shouldn't be removed.

Context Lines Display Discrepancy

Inspecting the Microsoft Word plugin code revealed that although most of the hard work to access the com objects etc. had been completed the code to display context lines was unfinished. The intention appears to have been to display context lines based on line and page numbers but the Word Application doesn't really support this. MS Word lines are actually paragraphs (each line word wraps and continues until a carriage return is inserted) and pages are only hard coded if you specifically add page...

There is another call to release the com object here: MicrosoftWordPlugin.cs public void Dispose() { if (__WordType != null && __WordApplication != null) { // Close the application. __WordApplication.GetType().InvokeMember("Quit", BindingFlags.InvokeMethod, null, __WordApplication, new object[] { }); } if (__WordApplication != null) Marshal.ReleaseComObject(__WordApplication); __WordApplication = null; __WordType = null; __IsAvailable = false; } I initially thought that this could be left in the...

Looks like this is the same problem reported in Bug No. 85.

Searching Multiple MS Word Documents