Hi Manuel,

This is the only thread in the world about a .override for Finalize(). I 
just stumbled across this because I am inserting Overrides for certain 
methods and now it suddenly failed. PEVerify said there was a duplicate 
MethodImpl (.override) entry. It turns out that Visual Studio 2013 and 
earlier did not generate this .override for the Finalize method at all. 
That's why I never noticed it. Now that I have upgraded to Visual Studio 
2015, the C# compiler always inserts this explicit override for Finalize. 
(I compared an old and new build of the same code.) Then I ended up with 
two of them.

I just wanted to say that this explicit override entry should not be 
necessary as long as you name your method "Finalize" (and probably make it 
virtual but not newslot) so that it can implicitly override that base 
method.

Interesting how compilers subtly change, sometimes breaking existing code.

-- 
-- 
--
mono-cecil
--- 
You received this message because you are subscribed to the Google Groups 
"mono-cecil" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to