Re: Calling .Net dll from Fox by Darwin
Darwin
Sun Feb 24 16:31:01 CST 2008
Yes, you are correct, I would have thought that COM registration would have
handled this through the registry.
If you just use regasm my.dll then the CLSID will be registered but NOT the
location of the dll. So you must use
regasm my.dll /codebase
This will store the location of the dll, otherwise you can place the dll
into the same directory as your VFP app and it will be found that way.
"Mike McCann" <mcsoft@cox.net> wrote in message
news:Ob4RDsvdIHA.288@TK2MSFTNGP02.phx.gbl...
>
> "Darwin" <darwin@nowhere.com> wrote in message
> news:OimXKjqdIHA.4164@TK2MSFTNGP05.phx.gbl...
>>I don't know where to post this because it runs across 2 languages but
>>here we go:
>> I have a class "ImageProcessing.captcha" it works correctly on the
>> development box but fails on the target machine.
>> It fails on
>> o = CREATEOBJECT("ImageProcessing.Captchas")
>> Error message "OLE error code 0x80070002: The system cannot find the file
>> specified"
>> There is no init code in the .Net class. The class was developed with
>> VS2005
>> The class has been registered with regasm which returned with "Types
>> registered successfully"
>>
>> The target machine has the 2.0 .Net framework installed.
>>
>> Any ideas?
>>
> IIRC, VFP doesn't know where the assembly registry is so you have to make
> a local copy of the dll available to your VFP program.