COM to .NET Framework 1.1 SP1 Problem

[Guest]

Hi,

Been building a nice integration layer between COM and .NET which worked
perfectly up until the moment I installed Framework 1.1 SP1.
The COM layer creates and initializes .NET classes registered as COM classes
and running in COM+. After installing SP1, the COM layer cannot create the
..NET classes any more, what I get instead is the following error "Declaration
referenced in a method implementation can not be a final method", the hResult
is -214622054 (80131522). The .NET classes compile just fine, and this error
comes up only in run time.
Further investigation led me to believe that this issue source is in .NET
classes that override methods of their base class: I noticed that if I change
the inheritance code and DO NOT override the base classes functions, the
problem goes away....but then again, it's no good, as the base class code is
running instead of the "real" implementation.

Please advise,
T.

 

[Richard Blewett [DevelopMentor]]

I've not come across this problem but have you tried making the overridden methods sealed, i.e.

public sealed override void Foo()
{
}

Regards

Richard Blewett - DevelopMentor
http://staff.develop.com/richardb/weblog

nntp://news.microsoft.com/microsoft.public.dotnet.framework/<[email protected]>

Hi,

Been building a nice integration layer between COM and .NET which worked
perfectly up until the moment I installed Framework 1.1 SP1.
The COM layer creates and initializes .NET classes registered as COM classes
and running in COM+. After installing SP1, the COM layer cannot create the
.NET classes any more, what I get instead is the following error "Declaration
referenced in a method implementation can not be a final method", the hResult
is -214622054 (80131522). The .NET classes compile just fine, and this error
comes up only in run time.
Further investigation led me to believe that this issue source is in .NET
classes that override methods of their base class: I noticed that if I change
the inheritance code and DO NOT override the base classes functions, the
problem goes away....but then again, it's no good, as the base class code is
running instead of the "real" implementation.

Please advise,
T.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.771 / Virus Database: 518 - Release Date: 28/09/2004



[microsoft.public.dotnet.framework]