locked
did windows runtime component rely on registry?

    Question

  • COM relies on registry to store class id and alike things. I am really confused if windows runtime component make use of registry to do something. what's the difference between them?

    Wednesday, December 21, 2011 2:22 AM

Answers

  • Hi Sky Driver,

     

    In general, Windows Runtime Component relies on registry to store activatable class ID, binary path, and alike things. Naturally, it differs from normal component in actual registry keys.

    For normal component, it usually makes use of HKEY_CLASSES_ROOT\CLSID, HKEY_CLASSES_ROOT\TypeLib, HKEY_CLASSES_ROOT\Interface, HKEY_CLASSES_ROOT\AppID, or similar keys to store information.

    For Windows Runtime Component, it usually makes use of HKEY_CURRENT_USER\Software\Classes\ActivatableClasses, HKEY_CLASSES_ROOT\ActivatableClasses,
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId
    or similar keys to store information.

     


    Best wishes,


    Robin [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Sky Driver Thursday, December 22, 2011 1:15 AM
    Wednesday, December 21, 2011 3:10 AM
    Moderator
  • This talk:

    Windows Runtime internals: understanding "Hello World"
    PLAT-875T
    Speakers: Matt Merry

    discusses how those registry entries are used. The registry entries above are internal runtime entries that most Metro style app or component developers would never need to use or manipulate.

    Was this a general curiosity question or was there a specific entry of interest?

     

    Thanks,

    -David

     

    • Marked as answer by Sky Driver Thursday, December 22, 2011 1:15 AM
    Wednesday, December 21, 2011 9:17 PM
    Moderator

All replies

  • Hi Sky Driver,

     

    In general, Windows Runtime Component relies on registry to store activatable class ID, binary path, and alike things. Naturally, it differs from normal component in actual registry keys.

    For normal component, it usually makes use of HKEY_CLASSES_ROOT\CLSID, HKEY_CLASSES_ROOT\TypeLib, HKEY_CLASSES_ROOT\Interface, HKEY_CLASSES_ROOT\AppID, or similar keys to store information.

    For Windows Runtime Component, it usually makes use of HKEY_CURRENT_USER\Software\Classes\ActivatableClasses, HKEY_CLASSES_ROOT\ActivatableClasses,
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId
    or similar keys to store information.

     


    Best wishes,


    Robin [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    • Marked as answer by Sky Driver Thursday, December 22, 2011 1:15 AM
    Wednesday, December 21, 2011 3:10 AM
    Moderator
  • This talk:

    Windows Runtime internals: understanding "Hello World"
    PLAT-875T
    Speakers: Matt Merry

    discusses how those registry entries are used. The registry entries above are internal runtime entries that most Metro style app or component developers would never need to use or manipulate.

    Was this a general curiosity question or was there a specific entry of interest?

     

    Thanks,

    -David

     

    • Marked as answer by Sky Driver Thursday, December 22, 2011 1:15 AM
    Wednesday, December 21, 2011 9:17 PM
    Moderator
  • Thanks guys! I want to dive into behind things for windows runtime component and compare it with normal comonent.
    Thursday, December 22, 2011 1:15 AM