Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP to .NET migration - form by form?
Message
From
05/01/2007 10:35:57
 
General information
Forum:
Visual FoxPro
Category:
COM/DCOM and OLE Automation
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01181837
Message ID:
01182797
Views:
25
Troy,

Sorry to be late getting you the files. I got sick and haven't been in front of the computer much the past few days. I'll try to package something up and get it out today.

The .Net assemblies will be registered on the development machine and will have to be registered as COM components on the client machine.

>Thank you. I look forward to whatever you can send.
>After building the .NET assembly (with the interop decorators), do I have to register the result unisng regsvr32?
>
>
>>My files are all at home. I'll get something to you later tonight. The Toolkit is basically a wizard that applies the lines needed to make the .Net class COM callable. The wizard only works for VB, but you can manually add the needed COM lines to a C# form and have it work.
>>
>>You don't add a reference in VFP. The .Net form is a COM component. You'll call it using CREATEOBJECT().
>>
>>
>>>Thanks for the reply. I have installed it and am trying to follow the examples. I have gotton as far as building the .NET form and registered the interop classes but could you perhaps provide a summary on how to make this work with VFP. For example: What would be the equlivent of adding a reference (I do not see Microsoft InteropForm Toolkit Library) as a COM control? Also, is this solution only applicable to VB.NET?
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer
Previous
Reply
Map
View

Click here to load this message in the networking platform