Re: None of the dll's contain type information!

I don't know why the TypeBrowser cannot extract the typelib info from the
dlls. Ask your friend to use DevStudio to extract the typelib from the DLL.
To do this he needs to open the resource view for the dll. Then there should
be folder named typelib. Under that folder will be a resource. Right click
that resource and click extract. Add the .tlb extension. Jawin should be
able to read this file.

Robert


-----Original Message-----
From: Discussion of Java/Win32/COM integration with Jawin
[mailto:[email protected]] On Behalf Of Josh Passenger
Sent: Monday, January 31, 2005 8:01 PM
To: [email protected]
Subject: Re: [JAWIN] None of the dll's contain type information!

Umm,

My appologies, I read .tld as .tlb

The type browser should be able to open a .tlb, I don;t know what a .tld
file is.

I believe it is possible for someone to generate a COM dll without type
information, its an optional thing.

Failing that perhaps AABB might be able to provide you with the TLB files
you need?

Josh

>
>Load up the .tld he generated, the TypeBrowser likes those,
>
>Josh
>
>
>>From: David Hay <[email protected]>
>>Reply-To: Discussion of Java/Win32/COM integration with Jawin
>><[email protected]>
>>To: [email protected]
>>Subject: Re: [JAWIN] None of the dll's contain type information!
>>Date: Mon, 31 Jan 2005 10:28:01 -0500
>>
>>They're dll's from Abbyy FineEngine.
>>
>>As I said, I'm a newbie at both Jawin and Com!  But, my colleague assures
>>me they are COM dlls, and their website states the same.
>>
>>My colleague uses them from C++, and imported them into Visual Studio and
>>created .tlh and .tld files for them.
>>
>>Can I somehow use these files?  If Visual Studio can extract that info
>>from the dll, should Jawin be able to?
>>
>>If not, would really appreciate any guidance on creating the stubs myself.
>>
>>Many thanks,
>>
>>David
>>
>>
>>
>>On Mon, 31 Jan 2005 10:30:29 -0500, Roger I Martin PhD
>><[email protected]> wrote:
>>
>> >Are these dlls that we would know?
>> >
>> >Their probably not COM dlls.  You have a header and lib file that goes
>> >with these dlls?  Need to write the dll interface by hand. The type
>> >browser only looks at COM enabled systems.
>> >David Hay wrote:
>> >
>> >>Hi,
>> >>
>> >>sorry - another newbie question.
>> >>
>> >>I have another package that I am trying to call through Jawin, but the
>> >>browswer says that none of it's dll's (that I can find) contain any
>>type
>> >>information.
>> >>
>> >>What does this mean, and is there a way around it?
>> >>
>> >>Many thanks,
>> >>
>> >>David
>> >>
>> >>
>> >>