Why file extension registries get added by default to HKCR?

Question

I am msi developer. In msi whenever we add registry comdata, it is preferred that, we should add it to HKCR. Is there any reason why we add it to HKCR? and not to HKLM? Even if we add it to HKLM, it reflects in HKCR.

Answer 1

Maybe this one helps.

http://msdn.microsoft.com/en-us/library/ms724498%28VS.85%29.aspx

 

---

Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]

Answer 2

Can anyone described the same in simpler way?

Answer 3

On Mon, 13 Feb 2012 04:59:34 +0000, MadForMsi wrote:

Can anyone described the same in simpler way?

http://msdn.microsoft.com/en-us/library/ms724475(v=vs.85).aspx

HKCR is not an actual storage location but rather a combined view of
HKLM\Software\Classes and HKCU\Software\Classes.

That's about as simple as it gets.

---

Paul Adare
MVP - Forefront Identity Manager
http://www.identit.ca
No line available at 300 baud.

Answer 4

I understood this point:- "Even if we add it to HKLM, it reflects in HKCR." because HKCR is replica of HKLM+HKCU, but why it is preferred to import registries to HKCR? why can't HKLM? Even if we capture comdat of any dll or ocs, in the reg file w get all the registries of HKCR. Why developers prefer HKCR, nd not HKLM?