| |
|
| Classification: |
C++ |
Category: |
Development |
| Created: |
11/10/2004 |
Modified: |
11/24/2004 |
| Number: |
FAQ-1163 |
| Platform: |
Symbian OS v7.0s, Symbian OS v8.0, Symbian OS v8.0a, Symbian OS v8.0b, Symbian OS v8.1a, Symbian OS v8.1b |
|
Question:
I have seen that there are two possible RegistryInfo.rh files that I could include in my ECOM plugin. Why does my ECOM plugin
not get registered when I am including RegistryInfov2.rh?
Answer:
As of Symbian OS 7.0s, the resource format for an ECOM plugin has changed to include new fields which are defined in the RegistryInfov2.rh file. This has been updated from the resource definition defined in the RegistryInfo.rh file. This newer resource header file extends the ECOM resource definition to allow ROM based ECOM plugins to specify whether
a ROM based plugin can be overridden by a RAM based one.
The RegistryInfov2.rh is only meant to be used by plugins which are ROM based, thus, its use is restricted. If you include
the RegistryInfov2.rh instead of RegistryInfo.rh file in your RSS file and do not define / set the additional fields (i.e. your definition conforms to V1), your ECOM plugin
will NOT be detected or loaded by the ECOM framework. Therefore, always include the RegistryInfo.rh file in your RSS file and avoid using the RegistryInfov2.rh resource header for a RAM based ECOM plugin.
More info on ECOM can be found here. DevKit users can look at ...\src\common\generic\syslibs\ecom\documentation\ECOM_RomOnly_HowTo.doc for more details.
|
| |
|
![[Index]](../../a_stock/btn_index_wt.gif){kind=small}
![[spacer]](../../a_stock/btn_spacer.gif){kind=small}
![[Previous]](../../a_stock/btn_prev_wt.gif){kind=small}
![[Next]](../../a_stock/btn_next_wt.gif){kind=small}
![[Previous]](../../a_stock/btn_prev.gif){kind=small}
![[Top]](../../a_stock/btn_top.gif)
![[Next]](../../a_stock/btn_next.gif){kind=small}