if I look into the ole/com viewer it shows that the IDispatch as being
there, or does it have to be setup as something other than the .Net default
Regards
Andrew Scott
Technical Consultant
NuSphere Pty Ltd
Level 2/33 Bank Street
South Melbourne, Victoria, 3205
Phone: 03 9686 0485 - Fax: 03 9699 7976
_____
From: Samuel R. Neff [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 6 January 2004 10:42 AM
To: CF-Talk
Subject: RE: CF MX 6.1 and com objects
Can't give you a complete answer but a part of one.
It has something to do with interfaces. CFMX requires the IDispatch
interface and something I read in a forum from a tech support person is that
.NET components don't expose this by default. The .NET docs indicate that
.NET COM wrappers are in fact dual-interface by default, so I'm not sure
what's up.
The solution was to add an attribute to the .NET component, but I don't
remember which. I just search the webforums and couldn't find the
thread--sorry.
Perhaps this will help you get on the right track...
Sam
-----------------------------------------------
Blog: http://www.rewindlife.com
Charts: http://www.blinex.com/products/charting
-----------------------------------------------
> -----Original Message-----
> From: Andrew Scott [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 05, 2004 6:13 PM
> To: CF-Talk
> Subject: CF MX 6.1 and com objects
>
> Hoping someone can help me out here, trying to create a com
> object with Studio .Net 2003. Now I have built the solution
> and .Net tells me I can use it in any application and that it
> is registered. However coldfusion can't create the object, is
> there a special trick to get a com object to work under CFMX.
>
>
> Any help would be appreciated..
>
> Regards
> Andrew Scott
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
