Hi scrap this one, I didn't realise vb.net creates a interop.mydllname.dll file which I also have to move
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Chris Davis Sent: 21 September 2011 15:21 To: [email protected] Subject: Re: Help with VB.NET VFP COM DLL Yes it is in references and the intellisense picks it up ----- Original Message ----- From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Wed Sep 21 15:16:51 2011 Subject: Re: Help with VB.NET and VFP COM DLL On Wed, Sep 21, 2011 at 8:54 AM, Chris Davis <[email protected]> wrote: > Hi All, > > I am currently working with a VB.NET project (not my own) and wish to use my > VFP COM DLL in it. I have created a very simple DLL for testing. The DLL > works fine from VFP but when I try and implement it in the VB.NET project I > get the following error. > > Could not load file or assembly 'Interop.mycomdll, Version=1.0.0.0, > Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system > cannot find the file specified. > ----------------- Did you register the dll in the VB project? -- Stephen Russell Unified Health Services 60 Germantown Court Suite 220 Cordova, TN 38018 Telephone: 888.510.2667 901.246-0159 cell [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
