Named ranges and COM Interop

Question

I'm familiar with the no double dot rule to avoid the dreaded:
COM object that has been separated from its underlying RCW cannot be used
However I'm unsure how this holds up for VSTO objects.  As far as I can tell I
would not need to release an object such as:
Globals.shtTime
As this is a native VSTO object (??)
However I would need to release the object:
Globals.shtTime.InnerObject
But is writing something like this ok?
Dim TargetRow As Integer = Globals.shtTime.rngMainTable.Row
I'm unsure whether that statement is creating a COM object that refers to my named range (rngMainTable)

Answer 1

Hello,
> As this is a native VSTO object (??)
You shouldn't release any objects that doesn't come from the Office object model. As an example - VSTO properties like Application and etc.
> But is writing something like this ok?
Yes, you are on the right avenue. You should release any objects that you got from the Office objects model. For example, if both objects (shtTime and InnerObject) belong to the Office object model (not VSTO) you should release
them if they are not received from VSTO properties.
> Dim TargetRow As Integer
= Globals.shtTime.rngMainTable.Row
Only VSTO developers can give the definitive answer in that case. We don't know the source code of VSTO. But the
ReleaseComObject method returns an integer value (new value of the reference count of the runtime callable wrapper associated with the object) which you can check each time. Thus, you will know
whether it is should be called or not.