Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFP to .NET migration - form by form?
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
COM/DCOM et OLE Automation
Versions des environnements
Visual FoxPro:
VFP 9 SP1
Divers
Thread ID:
01181837
Message ID:
01183344
Vues:
13
>After building the .NET assembly (with the interop decorators), do I have to register the result unisng regsvr32?

No. .NET Assemblies set up for interop need to be registered with REGASM.EXE.

There's more info here (towards the bottom):
http://www.west-wind.com/presentations/VfpDotNetInterop/DotNetFromVFP.asp

+++ Rick ---

>
>
>>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?
+++ Rick ---

West Wind Technologies
Maui, Hawaii

west-wind.com/
West Wind Message Board
Rick's Web Log
Markdown Monster
---
Making waves on the Web

Where do you want to surf today?
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform