com_module_sample
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| com_module_sample [2018/06/08 07:18] – wolfgangriedmann | com_module_sample [2018/09/04 03:52] – wolfgangriedmann | ||
|---|---|---|---|
| Line 95: | Line 95: | ||
| * to display the manifest in an application you can use this manifest viewer: [[https:// | * to display the manifest in an application you can use this manifest viewer: [[https:// | ||
| * 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.txt · Last modified: 2022/10/11 12:02 by wolfgangriedmann