I'll toss in 2 cents here. If you run your DLLs under MTS, you can also
execute the DLL in a separate user context. This is good if you use a
separate user account for CF and your DLL. THis way, if the DLL goes wiggy
and locks out its own account, you don't take CF with it.
> -----Original Message-----
> From: Maddison, David [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, July 04, 2001 6:54 AM
> To: Fusebox
> Subject: RE: VisualBasic COM Object Problems
>
> Nope we do it all the time here, and they run well. One thing I would
> advise, is running your ActiveX DLL's under MTS, so that if they crash
> they
> don't take down your CF server.
>
> Dave Maddison
>
> >> -----Original Message-----
> >> From: Dave DeVol [mailto:[EMAIL PROTECTED]]
> >> Sent: 21 June 2001 17:24
> >> To: Fusebox
> >> Subject: VisualBasic COM Object Problems
> >>
> >>
> >>
> >> Looking for input on using VisualBasic to create COM object
> >> dll's that will be accessed by ColdFusion as compared to
> >> C++/other COM objects. Any problems I'll run into?
> >> Limitations? Pros/Cons?
> >>
> >>
> >>
> >> Cheers!
> >> Dave
> >>
> >> --------------------------------------------------------------
> >> Dave DeVol
> >> Transfer Online, Inc.
> >> 227 SW Pine Street, Suite 300
> >> Portland, OR 97204
> >> [Phone] 503.227.2950 [Fax] 503.227.6874
> >> [Email] [EMAIL PROTECTED] [Web] www.transferonline.com
> >>
> >>
> >>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
