User Tools

Site Tools


com_module_sample

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
com_module_sample [2018/01/23 11:04] wolfgangriedmanncom_module_sample [2022/10/11 12:02] (current) wolfgangriedmann
Line 1: Line 1:
-====== Create a COM module for a VO application ======+====== Create a COM module for a VO application using XIDE ======
  
  
   * Create a prg file for the interface\\   * Create a prg file for the interface\\
-<code>begin namespace COMTest+<code visualfoxpro>begin namespace COMTest
  
 using System.Runtime.InteropServices using System.Runtime.InteropServices
Line 20: Line 20:
 The GUID needs to be created with the GuidGen.exe tool.\\ The GUID needs to be created with the GuidGen.exe tool.\\
   * Create a prg file for the functionality itself:\\   * Create a prg file for the functionality itself:\\
-<code>using System.Runtime.InteropServices+<code visualfoxpro>using System.Runtime.InteropServices
  
 begin namespace COMTest begin namespace COMTest
Line 50: Line 50:
   * edit the Init() method of the created VO class adding the cProgId and the cClsId using the GUIDs from your library. The cClsId uses the GUID from your class, the cIID the one from your interface.   * edit the Init() method of the created VO class adding the cProgId and the cClsId using the GUIDs from your library. The cClsId uses the GUID from your class, the cIID the one from your interface.
  
-<code>METHOD Init(ObjID, fROTCHECK) CLASS ICOMTester+<code visualfoxpro>METHOD Init(ObjID, fROTCHECK) CLASS ICOMTester
  
 self:cProgID := "COMTest.COMTester" self:cProgID := "COMTest.COMTester"
Line 64: Line 64:
   * move this manifest in the resources subfolder of your application directory (XIDE)   * move this manifest in the resources subfolder of your application directory (XIDE)
   * create there a file "Manifest.CREATEPROCESS_MANIFEST_RESOURCE_ID.rc" with the content   * create there a file "Manifest.CREATEPROCESS_MANIFEST_RESOURCE_ID.rc" with the content
-<code>CREATEPROCESS_MANIFEST_RESOURCE_ID RC_RT_MANIFEST "COMTest.dll.manifest"</code>+<code>#define RC_RT_MANIFEST 24 
 +#define CREATEPROCESS_MANIFEST_RESOURCE_ID 1 
 +CREATEPROCESS_MANIFEST_RESOURCE_ID RC_RT_MANIFEST "COMTest.dll.manifest"</code>
   * add this file to XIDE with Add Existing - Add Native Resources   * add this file to XIDE with Add Existing - Add Native Resources
   * build your DLL and check with a manifest viewer if your binary contains that manifest   * build your DLL and check with a manifest viewer if your binary contains that manifest
   * hopefully your VO application has a manifest. Add a reference to your COM dll:   * hopefully your VO application has a manifest. Add a reference to your COM dll:
-<code>  <dependency>+<code xml>  <dependency>
   <dependentAssembly>   <dependentAssembly>
   <assemblyIdentity   <assemblyIdentity
Line 89: Line 91:
   * you should set the namespace also in the project properties   * you should set the namespace also in the project properties
   * the exported class **cannot** have the same name as the COM DLL itself   * the exported class **cannot** have the same name as the COM DLL itself
-  * to debug your VO application:+  * to debug your SideBySide issues in your VO application (that may not start after changing the manifest):
 <code>sxstrace Trace -logfile:systrace.out <code>sxstrace Trace -logfile:systrace.out
 sxstrace Parse -logfile:systrace.out -outfile:sxstrace.txt sxstrace Parse -logfile:systrace.out -outfile:sxstrace.txt
Line 95: Line 97:
   * to display the manifest in an application you can use this manifest viewer: [[https://weblogs.asp.net/kennykerr/manifest-view-1-0|weblogs.asp.net/kennykerr/manifest-view-1-0]]   * to display the manifest in an application you can use this manifest viewer: [[https://weblogs.asp.net/kennykerr/manifest-view-1-0|weblogs.asp.net/kennykerr/manifest-view-1-0]]
   * Using the DispId attribute in the interface for every method makes sure that every version of your COM dll has the same DispId in the COM interface and you don't need to recreate the TLB file and the automation server in VO after every change. In fact, most of the time you should be able to adjust the automation server in VO manually if you change the interface of the COM library   * Using the DispId attribute in the interface for every method makes sure that every version of your COM dll has the same DispId in the COM interface and you don't need to recreate the TLB file and the automation server in VO after every change. In fact, most of the time you should be able to adjust the automation server in VO manually if you change the interface of the COM library
 +  * in many cases, the definition of the RT_MANIFEST constant in VO inhibits the correct loading of the COM assembly. In these cases, simply add the definition of the constant in your own program. Please see here: [[rt_manifest_constant|RT_MANIFEST constant]]
  
  
com_module_sample.1516705493.txt.gz · Last modified: 2018/01/23 11:04 by wolfgangriedmann