I'm using VS 2010 and need to make a change in an MSI installer.
I'm not that familiar with the installer creation -- it seems very limited.
I needed to add a new dialog that pops up and asks the user to select one of two possible installation directories. The dialog is the "RadioButtons (2 buttons)" dialog.
Depending on which radio button you select, the ButtonProperty sets TARGETDIR to either:
[AppDataFolder]MyInstall
or
[ProgramFiles64Folder]MyInstall
I have the DefaultValue for the button set to [ProgramFiles64Folder]MyInstall
I've got everything working -- at least when the user selects one of the radio buttons.
The problems are:
The default radio button isn't preselected when the dialog is displayed and it's possible for the user to advance to the next screen without selecting one of the radio buttons. How can I prevent that?
When the default value is set to something like [ProgramFiles64]MyInstall, on uninstall I get an error that it could not access the network location [ProgramFiles64]MyInstall -- even if that is not the location where the files were installed. If the path for the DefaultValue is a fully expanded absolute path, then there is no error.
With this code you van preselect the radiobutton: radiobutton.Checked = true
Related
I have a Windows Form application with a checkbox that presents different behaviour according to the user. The component appears in the form only for the user who installed first the application.
For other users that have the same privileges, in the same machine, the checkbox is not visible. I already tried to uninstall and reinstall the application with different users, but the problem persists.
In my code, there´s nothing that changes the Visible property to true or false, I just let the default value to true
Appreciate any help, thanks!
Try resize the window that contains the checkbox. You are probably setting the size or the location of the checkbox in a wrong way. Try to use proper anchor property and see if the problem resolves.
I want the following behavior in a WiX installer:
a "read and accept EULA" dialog is displayed
a "select folder" dialog is displayed
files are copied to the target folder
a custom dialog is displayed requiring some action from the user and entering a specific string of characters into an edit box on the custom dialog
a custom action runs an executable from inside the target folder and passes the string entered into the custom dialog
... and no, the string which is entered into the custom dialog is not known until the files are copied and the user does the action required from him.
I've searched quite a lot and it looks like there's a "UI sequence" which shows dialogs in certain order and there's an "Execute sequence" which copies files and runs custom action. And it looks like I cannot interleave them.
Is the sequence I described above even possible?
I'm building an installer where a given page is asking for a directory. Unfortunately I'm not allowed (by the customer) to force an initial value into the entry (it must be blank), so using PathEdit is out--I have to use a raw Edit control. I've added a Browse button that invokes the BrowseDlg, but the question is: how to show the value entered in the browse dialog?
I've seen recommendations of duplicating the original page, since I can't update the original textbox on the initial page. While that seems workable, how can I get to the 2nd copy of the page? The button to open the Browse dialog invokes SpawnDialog. Doing it as a NewDialog looks really cheesy, and doesn't match the use of Browse dialog for the installation location, where it just pops up. But when the SpawnDialog returns, it just stays on the same page. There's no condition I could come up with that would allow me to add a NewDialog to go to the 2nd page, or to any other page for that matter.
Any ideas on how to proceed, so I can show the entered Browse value?
I suggest using a custom action and an edit box similar to this post. You can use a FolderBrowserDialog instead of the OpenFileDialog. It works for me, but upon a second install the field will be populated with the previous value.
http://community.saasgrid.com/developers/b/team/archive/2011/02/17/wix-managed-custom-actions-openfiledialog-example.aspx
I'm running with an 8.5.3 UP1 server and I have a need to have many dialog boxes (for confirmation purposes) for a whole bunch of "action buttons" on an xpage. The code for these dialog boxes is almost exactly the same with the exception of the confirmation message being different and the client-side JS function they are calling if the Yes button is selected.
Since I really hate repeating code over and over, I was wondering if it is at all possible to put a xe:dialog control within a repeat control and specify the message and function call from an array of values? I know I can't compute the ID of the dialog control and without that I'm not sure how I would reference the dialog to open and close it.
Any ideas? Thanks
Yes, this is possible.
Make sure that you specify that the dialog box's property for keepComponents is set to False. You don;t have to do anything special for opening or closing the dialog box, just use whatever ID you give the dialog box in you client-side action to open the dialog box in the repeat such as XSP.openDialog('#{id:myDialog}')
The XPages renderer will automatically calculate the correct ID names for you.
I have downloaded the newest version of Wix Toolset and have made a custom dialog to get the connection string for the database from the user. When I test run the Msi on a Windows 7 machine, the dialog box is there as well as my display text, but the edit control is not showing up. If I click on where it is supposed to be, I get a cursor and if I start typing then the white background on the textbox shows up. Is this a bug?
Almost certainly this is a Z-order problem where another control is overlapping with the control you want. First, ensure your controls don't overlap. Then, order them in the Dialog element such that the highest z-order are last (IIRC).
I had a similar issue where the edit boxes were "invisible" until I clicked on them. After examining the code, I realized that my controls were being "painted over" by my dialog bitmap. I made the bitmap code the first line in the dialog and this fixed the problem as the controls got "painted over" the bitmap.