Hi All,

Can Anyone Explain me what are HKCR\CLSID\{ }\InprocServer32\ThreadingModel
Registry Entries....
Cant we delete these entries when they are present in COM Registration(in case of MSI's)??? Is it necessary to keep the CLSID entries even when they are coming from COM Registration(in case of MSI's).


Thanks in Advance,
Dev
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
0
Although it's possible that things will still work without a particular threading model being specified for the server, I would prefer to assume that it has been specified for a reason.

Deleting the entry from he registry table will mean that the entry probably won't be written to the registry unless a selfreg table entry exists to do the registration instead.
Answered 12/27/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
0
Hi WiseUSer,
Thanks for ur Reply, But when we have these registry entries(InProcServer32\Threading Model) in COM Registration(CLASS Table of MSI) why are they not getting created in some cases in Registry?????
Do You mean that the application will not Function Properly if we delete these InProcserver32 registry entries in Registry Table of MSI(As these are present in COM registration).

What Exactly are these InProcServer32 registry Entries, What are there Specific Functionality?????

Thanks
Dev
Answered 12/27/2005 by: DevGowda
Orange Belt

Please log in to comment
0
I never touch registerfiles inside HKCR. I always keep these intact and I never experienced any problem with it.

I think it takes alot more time to sort them out that what you get out of it.
Answered 12/27/2005 by: Gastro
Senior Yellow Belt

Please log in to comment
0
The "Class" table should create the "InProcServer32", but I'm not sure that it will ever create the registry key that specifies the threading model? I know that the SDK refers to "the path to a 32-bit in-process server and the threading model" when defining the "Context" column of the "Class" table, but I've never seen the threading model specified here.

The InProcServer(32) and LocalServer(32) provide the path to the "server" (dll, ocx or exe) for the component. When these entries are created through the MSI "Class" table, an extra entry is created which represents an advertised entry point to the MSI installation. This entry point is only used by shells that are advertising-aware, OS versions prior to NT4 (and early NT4 SP levels) will use the default (readable) path to the component.

I would recommend that you leave these registry entries as they are unless you have a specific reason to modify/remove them?
Answered 12/27/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity