Using the old COM in. Net makes people feel a headache!

Using the old COM component in. NET is also non-. Net COM, which is often confusing !!! WrittenProgramIt is possible to run all the OK statements in the header, but it is inexplicable to let it run several times. Exceptions are strange. I had to find a solution.

Google, I saw a friend's post mentioning the solution. "In. net, when calling the unmanaged COM component, it is actually indirectly carried out through RCW (runtime callalbe wrapper). Therefore, we must follow some rules when calling. For objects returned from the unmanaged COM component, we need to call system. runtime. interopservices. marshal. only when the releasecomobject () method is set to null can it be correctly released and its normal operation be ensured. In particular, some objects that are implicitly returned must be called like this .", I also think that the LJ recycling mechanism of. NET is to be changed. Otherwise, let the hackers try to press the keyboard multiple times !!!

I hate reading the technical documentation in msdn. This time, it seems I am still going to suffer. I don't know how. NET 2.0 works in this regard?