I have two questions here.

I have captured an application in which i get the following registry

HKEY_CLASSES_ROOT\MSComCtl2.Animation value=Microsoft Animation Control 6.0 (SP4)

and the registry i have already in system is

HKEY_CLASSES_ROOT\MSComCtl2.Animation value=Microsoft Animation Control 6.0

First question is

What is the difference between two? and I am not sure if I can consider this as a garbage and delete from msi since the value is getting differed.

keeping the registry is also not the solution since when the app is unistalled it will delete the registry.

So what I have done is I have moved all these type of captured registries to HKEY_CURRENT_USER\Software\Classes. It worked fine I mean when I install the application i get the captured value in HKEY_CLASSES_ROOT\MSComCtl2.Animation and when i uninstall the application it will get back to the original value.

My second question is

Is this the correct method what I am doing or my thinking is totally wrong?

Your help is much appreciated.

Thanks in advance.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Naveen,

For cases like this, you should check the CLSID and look for the actual file who owns it and move it to that component. If you have added that file as a merge module, then you can simply delete the keys. This is all part of a cleaning up process after you have just captured an application and should be part of your basic steps. When I checked it is from "C:\WINDOWS\system32\mscomct2.ocx". Hope this help.
Answered 05/05/2011 by: dj_xest
Fifth Degree Black Belt

Please log in to comment
0
Dj,

Thanks for your reply.
Yes its a basic step but got little bit confused here. Yes it is the same file but I have near about 30 registries which all are of this type and almost all are merge module files only. But when i check merge modules I can see the value which is already in system i.e Microsoft Animation Control 6.0. So i got confused here that what does that extra (SP4) means. Ofcourse i will add merge modules and delete those files but wanted to make sure with you guys whether i can delete that captured registry (Microsoft Animation Control 6.0 (SP4))

And is my second method the right way to do?(may be not with these registries but if we have any other registries which do not have merge modules and which conflicts with system registries with different values).

Thanks.
Answered 05/05/2011 by: naveen.packager
Green Belt

Please log in to comment
0
Clearly:

- your package is installing SP4 of the MS Common Controls whereas your packaging machine has the originals
- by moving the data to HKCU, you may be changing the registration from per-machine to per-user.
- you should remove the ".packager" part of your nickname for a while.
Answered 05/05/2011 by: VBScab
Red Belt

Please log in to comment
0
ORIGINAL: VBScab

- you should remove the ".packager" part of your nickname for a while.



oh my ribs. they hurt!
Answered 05/05/2011 by: kardock
Second Degree Green Belt

Please log in to comment
0
VBScab,

I expected this type of reply from you. I do agree that this is a basic thing that the packager should know. But I am little bit confused here. This may be a very very silly question to you coz u r genious. But I am not. Your reply is discouraging.
Answered 05/05/2011 by: naveen.packager
Green Belt

Please log in to comment
0
Your problems as a "packager" are deep-rooted if you don't know what the initals 'SP' mean in a software context.

Whether or not you use updated files is a client call. There may be good reason that he might want to stay with the original file versions. Of course, there's always isolation to consider as a kind of work-around
Answered 05/06/2011 by: VBScab
Red Belt

Please log in to comment
0
VbScab,

I knew SP means Service Pack and SP4 means Service Pack 4. But I am not aware of MS Common controls Service Packs (may be i should have known this earlier). And I have Merge modules for originals. So I am bit confused what to do and this is the reason I have raised he question.
Answered 05/06/2011 by: naveen.packager
Green Belt

Please log in to comment
0
MSComCtl2 always comes as merge module (MM). I recomend you using MM instead of hardcoded regsitry values/files.
MM name is "Microsoft Windows Common Controls"
Answered 05/07/2011 by: itolutions
Orange Senior Belt

Please log in to comment
0
i would suggest you look into prog id versioning.

you can have multiple links to a single progid reference

you can reference the appropriate version of progid using the .\curver reference

i strongly suggest you work out what comctl is or you risk toasting all sorts of interesting things but it makes for fun troubleshooting if you wish to ignore it.
Answered 05/08/2011 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
0
Thank you john.
Answered 05/10/2011 by: naveen.packager
Green Belt

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