Anyone know what the deal is with the .NET COM object wrapper and Cold
Fusion? Is it true that parameterized functions in .NET assemblies just
don't work? Anyone know if there is a work around for it or a slated fix for
this issue in Neo? I have to say it is rather troublesome and kind of
destroys the potential componentized development with .NET and Cold Fusion
integration. You think with every other object architecture and it's mother
being supported (at least in a semi-functional level) with CF that the .NET
integration would be the same. 

Erik Yowell 
Senior Web Developer 
Web Services 
Spherion Corp. 
mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>  

 

______________________________________________________________________
Dedicated Windows 2000 Server
  PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER
  Instant Activation � $99/Month � Free Setup
  http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to