Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP7 and DotNet Framework.
Message
De
20/11/2000 17:22:45
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00443342
Message ID:
00443867
Vues:
16
>Makes sense. And the docs *do* say that it just can't be invoked, says nothing about visibility via the typelib. With all of the "built just yesterday" software I've got installed, believe it or not there isn't a single object on any of my work boxes that shows as implementing this interface.

But how would you know? :-)

FWIW, I have a couple of System created COM+ apps on this box whose components will allow me to set them as Poolable. IISWAM.W3SVC in "IIS In-Process Applications" for one. I checked this object in the object browser, and sure enough, IObjectControl doesn't show as an inherited interface. Hmm.

>Works for me. Are you looking in the CoClasses for the implemented interfaces?

Yup. My methods show up, but all under the default interface IMyObject. I know that the IMPLEMENTS Word is getting looked at, because if I change the name of the dll file it references, the compile chokes. Is it possible that the Miami release doesn't do this correctly, or is it more likely that I am experiencing cerebral flatulence?
Erik Moore
Clientelligence
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform