
aaronmclean1.5524946233972285E12 asked a question.
Quality Monitor question
I just started working with Quality Monitor in Admin Studio 5.0 SP1 and had some questions.
In the Class ID view, under the failed items, is there an explaination why these items didn't register? Does Quality Monitor suggest dependant dll's or ocx's that are missing and are needed to register my failed file correctly?
Also, I don't think that Quality Monitor is reporting Failed Class ID's correctly. I walked through a couple of of failed Class ID's and it looked like the dll actually registered correctly.
Any help would be appreciated.
Thanks!
Right now QualityMonitor does not display the dependant Dlls. We will consider adding this in future.
For verifying the validity of the classid, we call CoCreateInstance and query for IUnknow interface which is the basic interface any COM component should support.
A call to CoCreateInstance could fail, even if the DLL is registered properly.
Regards
Rajesh Tammana
I was really hoping this tool would proivde usefull info, like a better Dependency Walker.
I wonder if I am missing anything, but as far as I can tell Qaulity Monitor may be telling me something important but I won't be able to tell because of all the false positives/negatives.
You may want to try Runtime tests feature which monitors the actual execution of the applications and and reports the runtime errors. So in your case, by actually running the application you would know whether the COM component is registered properly or not.
Regards
Rajesh
Couldn't I just run the package on my own and see the package fail becaue of the dll not being registered?
I'm not trying to be a jerk, but can you suggest any other parts of Quality Monitor that are extremely valuable?
Is there any way we could get the package you are working with and try to reproduce the issues here.
By having the application here, we can dig more into the COM class reporting issues and runtime tests.
Pls. contact me at rajesht@installshield.com
Regards
Rajesh Tammana
Thanks!
Joe
Thanks!
We could have designed QualityMonitor to just check that the registry entries exist but we wanted to take it a step further and see if these CLSIDs and ProgIds would actually execute. Since all COM objects inherit from IUnknown, in theory, we should be able to create an instance of that object through IUnknown. However, it may turn out that in reality, this check is a bit too stringent.
It is possible that these objects fail because of dynamic dependencies, or some configuration is wrong, or some other objects need to be created first. It is also possible that the application may still work because it may not use those objects, or it knows how to use them. Or it may be a problem with the installation. It will vary from case to case.
We welcome input on this feature and we will see what we can do to improve the overall experience.
Joe
Here are some suggestions:
1.) Can you add the dynamic and static scan that are in Developer to Quality Monitor and report the missing dependencies?
2.) If a particular ClassID or ProgID 'fails' can you give a verbose report why it failed? Maybe indicate what registry entries were successfull and which ones were not. Or add any other info that might be important.
3.) Can you add a complete file scan to Quality Monitor that verifies which files actually got installed by the package? If certain files didn't get installed, check to see if their component/ feature had a condition and then list that condition as to why those files didn't get installed. Reporting the file attributes would be great too (read only & hidden are sometimes a problem).
Thanks!