Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Isolated VFP DLL in .Net app
Message
 
 
À
27/06/2005 18:34:44
Information générale
Forum:
Visual FoxPro
Catégorie:
VFPX/Sedna
Versions des environnements
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
Visual FoxPro
Divers
Thread ID:
01026875
Message ID:
01026892
Vues:
13
>>In your Sedna preview you showed a VFP DLL (?) with the Isolated attribute integrated in a .Net solution, where the reg values apparently go into the manifest, making ClickOnce / XCopy deployment possible.
>>
>>Could you please share the explanation / a sample how to do this?
>>
>>How about the runtime or wrapping up a beta for a residue-free uninstall?
>
>I'm not sure what you mean about asking how to do this. The Ch9 video showed how to do this. You add the VFP DLL to the VS 2005 project as a COM rerference, set the COM reference to Isolated = True, and then build the VS project. This has nothing to do with XCopy deployment. Let me know if this clarifies, and if not, maybe be more specific.
>
>Note: When you want to ask me a question directly on the UT, it may be helpful to direct it to me and not All to be sure I read it.

I don't know if the confussion is something like this, Guenter, but the important thing is that this deployment method only works for the .NET application consumption. When you use this feature the DLL is NOT registered, and then it doesn't need to be unregistered at all. Also, you CAN'T instantiate it from a COM environment (i.e: other VFP application) in the target machine (except that it the DLL is found in the app path, but this is not the proper way to do things).

Please, Ken, let me know if I'm wrong at this.

See you,
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform