Is there a way to avoid displaying help link in control panel using installshield for a basic msi project? - installshield-2012

Is there a way to avoid displaying help link in control panel using installshield for a basic msi project?
I have a basic msi project. Help link that appears in Add/Remove programs of control panel needs to be removed. Other properties such as Support link,Update information needs to be retained.
Is there a way to remove Help link?
Thanks in advance.

This sort of thing is native Windows Installer functionality. You might ensure that the properties ARPHELPLINK and ARPHELPTELEPHONE are empty, to see if that provides the desired behavior. If not, I don't see any obvious way to influence this.

Related

Where can I find the source code for built in dialogs (WelcomeDlg, ErrorDlg, etc)?

I've built an installer based on WixUI_FeatureTree.wxs. I now need to add a third page with some additional controls. I would like it to look the same as CustomizeDlg in WixUI_FeatureTree.wxs. Where can I look to find where it's created/defined.
I understand there may not be a WXS file for it, but I still wanted to look at where it's created/defined so I can build an identical dialog using all the same properties.
For WiX Toolset v3, you want the UIExtension.This is WixUI_FeatureTree.

Can we localize WIX msi and bundle using language selection UI at runtime?

We have an MSI and Bundle created in Wix. I need to localize both of these in such a way that language selection GUI will be popped-up and language can be selected by the user at run time. Would be really appreciated if anybody can help me on this.
For MSI, i am working on creating another bootstapper for bringing-up with language selection combobox and invoke the tranfomed MSI with the required transform(using command shell). I am still not sure about the feasibilty of this approach. I am facing issue in creating combo box in customized UI of bootstapper and invoking batch command to run this msi in the required language.
For Bundle - I am still working on finding a method. if anybody has any idea/samples for this.
It will be helpful if anybody can help me with this issue or provide me with an another alternative method to meet above requirement.
Thanks,
The recommended method (and for that matter, the method used by most MS products), is as you describe.
Create an MSI localized for each language
pick a base and generate MST's
Package the MSTs, the MSI and the bootstrapper, which will
present the language selection dialog and call MSIEXEC, passing TRANSFORM=language.mst as an argument
After the MSIEXEC process has started, all localization is finalized, so to speak. Any selection must go on outside the MSI system.
See this codeproject article for an example.
I guess this may help you:
creating language selection dialog using WiX.
there is a limitation that custom UI for language selection is created using C# based custom bootstrapper. This may lead to the requirement of .Net framework on host machine.
UI selection for MSI
Create an MSI localized for each language
Pick a base and generate MST's
Package the MSTs, the MSI into a bootstrapper.
Customize the HyperlinkTheme.xml to include radio button for selecting each language.
Use the Variable tag to link radio button from UI to .wxs file
Include the msi property in the msi tag and hard code the path to MST's and InstallCondition attribute to differentiate each selection
Use the latest version of wix for this feature support.
Bundle support only automatic base detection there is no support for UI selection

WIX Feature Tree with Checkbox selection

I am in need to add a Features tree with checkbox selection to my msi. Can any one point me to some sample as how to achieve this please?
I already have one Feature element (ProductMain) that installs all the mandatory components. I have tried using the built-in CustomizeDlg and FeaturesDlg but not sure how to change the Selection tree to use Checkboxes
I am using WIXUI_Common set of dialogs.
I would appreciate any suggestion/guidance in this regard.
Sincere thanks!
You're limited to the UI supported by Windows Installer (which is quite limited). I don't think you can customize the SelectionTree control to display checkboxes. Alternatively, you can emulate the desired behavior by placing a number of checkboxes on a dialog and implement a certain logic to set feature levels.

Providing help documentation in VB.NET?

I have written up troubleshooting documents for my project and would like them included in my program. I remember in VB6 there was a very easy way to do this with a control, where it already has the help document tree set up on the left and you just set it to point to certain files.
Does something like this exist for .NET? I am aware of the HelpProvider control but as far as I know this just puts in tooltips and opens documents on a button press?
Thanks for any help. :)
To the best of my knowledge no such interface exists in Visual Studio, at least in the express editions that I have installed here. As your investigations showed you, the only way to provide help is to add a HelpProvider to a form and set its HelpNamespace property to your HTM/CHM file. Then on each control you can manually set the HelpKeyword, HelpString and/or HelpNavigator properties. Setting the last option controls how the values of HelpKeyword or HelpString are passed to the external help file.

WiX Show Dialog Based on Feature to be Installed

Let me be upfront I am novice with WiX. I have a custom dialog CustomSetupTypeDlg.wxs that changes the Typical/Custom/Complete to Desktop/Server/Suite. It sets WixUI_InstallMode to InstallDesktop, InstallServer and InstallSuite appropriately.
I need to have the user browse for an installation folder depending upon what feature is to be installed. If InstallDesktop or InstallSuite is selected the user has to select two different paths for DESKTOPINSTALLDIRECTORY and SERVERINSTALLDIRECTORY. However if the install mode is InstallServer only SERVERINSTALLDIRECTORY choice should be presented.
I am uncertain on how to go about doing this.
You want to have actions in your InstallExecute sequence that display the dialogs you need. Inside the tag you provide a conditional, which, when true, causes the action to actually happen. See this tutorial, specifically section 5.3 for a list of conditionals.
I decided to simplify the project by splitting the desktop and server features into two separate installers.