Should the lack of responses (neither negative nor positive) tell me that nobody ever tried to distribute pb assemblies to PB developers and then to c# developers?
I'd attribute it to:
1. Busy developers (at least in my case) and
2. Rather critical data missing from the question.
With regards to the second item:
Are you creating the assembly using PowerBuilder Classic or PowerBuilder.Net?
What version are you using?
You reference "either PB or .NET assemblies": Assuming you're using PowerBuilder.Net, PB Assemblies and .Net Assemblies are completely different things. A PowerBuilder.Net PB Assembly is the equivalent of a PDB in PowerBuilder Classic, a method of providing precompiled PowerBuilder code to other PowerBuilder.Net developers. A PowerBuilder.Net .Net Assembly is C# code that can be shared with both PowerBuilder.Net developers (and PowerBuilder Classic developers as well) and Visual Studio.Net developers.
What I did try with PowerBuilder.Net 12.5.2 was to create a PowerBuilder.Net .Net assembly target with two classes:
n_ancestor with function of_ancestormethod
n_descendant inherited from n_ancestor and with of_descendantmethod
I made sure that in the project I selected both of the methods on n_descendant to be exposed in the assembly (and nothing on n_ancestor).
I included that assembly in a Visual Studio.Net project and was able to reference both methods of the n_descendant class.
I then created a C# class that inherited n_descendant. I created a method on it that was able to access the ancestor methods. I also was able to create C# code that used the C# class and call the ancestor methods directly.
Perhaps you could explain what you're doing that is different from what I did, as what I did seems to be working fine.