M
Mike Fechner
Guest
ABL types cannot be loaded as assemblies. Best chance you may have is to define .NET Interfaces for everything the .NET side (your editor) needs to “see”. ABL classes implementing those interfaces (and inheriting from System.Object) can be used from the .NET side (only the members – methods, properties, events – defined in the interface are visible and accessible to .NET). But .NET cannot NEW an ABL object, even when it implements a .NET interface type. Your editor will probably use .NET reflection. This requires System.Type’s not Progress.Lang.Class. Hybrid ABL types have both – but the System.Type view of it, will only contain methods, properties, events of what’s required for the .NET interfaces – or what overrides .NET methods. The .NET Types for the hybrids will only be emitted (created) in the dynamic assembly, once an instance of that type was NEW’ed from the ABL side. Laura will probably correct me in a few hours
Continue reading...
Continue reading...