Strongly typed methods and properties

re: Strongly typed methods and properties

Rick Strahl — Mon, 05 Sep 2005 09:37:59 GMT

Looks like there's a small bug with the type casting:

CASE nType=3
cstr = cstr + "int"
*cstr=cstr+ "integer" // invalid

The Midl compiler failed on me when I had an integer value in the inbound parameters. Works well now.

Just for others who want to wrap this up other than a project hook you can just put the class into a PRG and do:

LPARAMETERS lcDll

IF !EMPTY(lcDLL)
o = CREATEOBJECT('FixTypeLibrary')
? o.FixTlb(lcDLL)
ENDIF

#DEFINE VS_PATH "D:\programs\vstudio2003\Vc7\bin\vcvars32.bat"

Note I renamed the class and replaced the hardcoded VS path which might be a good idea. No heavy duty testing here, but it works for the simple scnearios I tried generically. Cool

FoxPro and COM typelibrary creation

Rick Strahl's WebLog — Mon, 05 Sep 2005 09:51:00 GMT

If you're using COM with VFP you may have run into a nasty problem that doesn't allow VFP to create a typelibary containing parameters, return values or property types of other classes/interfaces that exist in the current project. Calvin posted a solution to this problem the other day and here is some additional information around the topic.

re: Strongly typed methods and properties

Craig Boyd — Mon, 12 Sep 2005 06:53:15 GMT

Calvin,

My reaction is the same as Rick's... Cool!

re: Strongly typed methods and properties

Anatoliy Mogylevets — Thu, 24 Nov 2005 02:08:59 GMT

Calvin,

This is great! Thanks for sharing your knowledge with the community.

You preserve 2 sections of EXE before updating the resources. As I understand, without this nice trick, VFP dll or executable would be damaged/truncated.

If possible, could you explain why this is required. Is there someting wrong with the UpdateResource API, or it's just because of some specifics of VFP executable format?

Thanks!

re: Strongly typed methods and properties

Dan Thomas — Sat, 07 Jan 2006 00:48:23 GMT

It appears that strong typing with more than one method parameters generates an midl compile error?...

FUNCTION MyMethod (MyParam1 AS integer) AS integer
... this works

FUNCTION MyMethod (MyParam1 AS integer, MyParam2 AS string) AS integer
.. this generates errors during the midl compile

Any ideas?

My homepage

Dennis — Thu, 21 Dec 2006 05:33:44 GMT

Thank you!

[url=http://pmmdwqkn.com/grll/hsqc.html]My homepage[/url] | [url=http://vpgylnxb.com/jfox/nmss.html]Cool site[/url]

Add a manifest to control your application Vista UAC behavior

Calvin Hsia's WebLog — Sat, 14 Apr 2007 00:32:08 GMT

Try this on Windows XP or Vista (I don’t remember if manifests are allowed on Win2000: can someone confirm

Allowing Optional parameters in your COM objects

Calvin Hsia's WebLog — Thu, 17 May 2007 04:31:39 GMT

It’s simple to create a VFP object that can be used within other applications. I show how useful it is

re: Strongly typed methods and properties

Jon Goad — Fri, 09 May 2008 22:17:08 GMT

I had to change this line:

strTlb=FILETOSTR("t.tlb")

to this:

strTlb=FILETOSTR("tlibtest.tlb")

Without this change, it gives the error that the file t.tlb does not exist.

re: Strongly typed methods and properties

TZuidema — Tue, 03 Mar 2009 17:04:06 GMT

Hi,

At the end, when the (2) sections are restored to the EXE, the order of the sections is reversed.

That prohibited COM registration on our EXE.

So instead of the last FOR i = 1 TO 2, use

FOR i = 2 TO 1 STEP -1

Regards,

Timo.