Strongly typed VB typelib please

[gtsoftware]

Hi,

I'm moving an application from driving Rational Rose to driving EA instead ( 6.1.788 ). Apart from the pleasure of using EA, I find that the object model often leaves me floundering in the land of untyped Objects which I then have to figure out the real type for. The various collections are the worst for that.

I'm sure I'll just get to learn what object to expect where but I'd still prefer strongly typed objects everywhere if possible.

Keep up the good work

[«Midnight»]

Yes!

The automation model clearly dates back to the land of COM, and particularly to VB 6 (or earler). There was little if any provision for overloading function signatures. [This was a gift from the designers of COM, rather than a limitation Sparx imposed.]

I gather that the idea was that all collections would work the same; that is, all of them provide a standard return type of "Object." Since the Interop interface is a .Net wrapper for the COM back end, it inherits the inability to provide additional signatures. [At least it has this 'out of the box.']

All this said, I heartily second your suggestion. It would be a godsend to have strongly typed functions, freeing us from a quagmire of type casting.