Rick, That is brilliant... it'll make a nice addition to my .NET integration posts eh... thanks!
Mark A. Kruger, MCSE, CFG (402) 408-3733 ext 105 Skype: markakruger www.cfwebtools.com www.coldfusionmuse.com www.necfug.com -----Original Message----- From: Rick Root [mailto:[email protected]] Sent: Tuesday, December 07, 2010 4:06 PM To: cf-talk Subject: Re: .NET errors after CF 9.01 Update Alright, thanks to the kind folks at SupportObjective (www.justcf.com), we figured out this little tidbid. Apparently, Coldfusion's .NET integration when installed on Win7 64 bit can call both 64 bit and 32 bit DLLs. However, it creates the dotnet proxy DLL dynamically when first called - and we were calling a system DLL from the 32 bit framework. So, after stopping the services, deleting all of the cached jar files in the dotnetproxy folder as well as the dotnetcoreproxy.jar in the same instance, and then making sure to FIRST call a DLL from the 64 bit framework... then everything is fine - including calling DLLs from the 32 bit .NET framework Rick ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:339899 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
