/build/static/layout/Breadcrumb_cap_w.png

How to Suppress registration wizard in Crystal Reports 9

Hi,
My application name is Crsytal Reports 9.0 . This is an extracted MSI. I have created MST for this. I need to suppress one registration wizard (regwiz.exe). After installing the application I am able to launch the registration wizard from Help menu of application shortcut. But I need to suppress this registration wizard.
In Crystal Reports 11.0 I have given one property i.e,. INSTALLSWITCH=Client to suppress this registration wizard. It wasworking fine for this application.

I applied the same thing in Crystal Reports 9.0 but it is not working.

Can any body help on this.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: timmsie 16 years ago
Fourth Degree Brown Belt
1
Not entirely sure what you mean but in version 9.2.2.5705 I removed the custom action -

LaunchRegWizAction.6F2B3983_59B8_11D3_B360_00A0C9DA500E

from the installExecuteSequence and removed the shortcut.

regwiz.exe.6F2B3983_59B8_11D3_B360_00A0C9DA500E

If you want to get rid of the file completely then remove the component regwiz.exe.6F2B3983_59B8_11D3_B360_00A0C9DA500E

Obviously all with the aid of a transform and not editing the vendor msi direct

Just because CR 11.0 works by setting the property INSTALLSWITCH=Client it doesn't mean v9 will. In 11.0 I'm guessing that the component or custom action have a condition on them which relates to the property. But In v9 there are no such conditions.
Posted by: sanhivi 16 years ago
Third Degree Green Belt
0
I commented teh custom action related to regwiz. I removed the shortcut from the application. Still I am getting the registration window from the Help menu of the main shortcut.
If I remove the component related to regwiz then it is not showing this wizard. But this component related to merge module. As per the standard we shouldn't remove the merge module related files and registreis.
Is there any other solution for this.
Posted by: anonymous_9363 16 years ago
Red Belt
0
As per the standard we shouldn't remove the merge module related files and registreis.What standard? Whether a component is in a merge module or not, it makes no difference. If you don't want something to be installed, don't install it!
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ