I would like to show the my custom dialog rather than the message box when Launch Condition failed in Wix. Normally, the message box of Launch Condition has OK button, but I would like to make more than that with some further actions with my dialog.
Could you please advise me how I can make it?
Thanks.
Dialogs can be sequenced using the InstallExecuteSequence and Custom elements. Schedule it prior to your Welcome dialog and after the LaunchConditions action. You may want an error custom action scheduled in the execute sequence to handle logging during silent installs.
You may also want to author your dialog into the main wizard loop (after install welcome ) using Publish elements also. It's hard to say without understanding your exact needs.
Related
I'm updating an InstallShield based installer. I've added a new managed custom action, written in C#, and packaged using Wix DTF.
Action is invoked correctly, and performs necessary actions.
Problem I have is showing an error message to user.
Method 1: MsiProcessMessage
From articles I've read, I understood that MsiProcessMessage is the correct way to do it, however this method does not work in UI sequence (before setup actually starts copying files and modifying system). In install sequence this method works. Code which I use is following:
Record record = new Record() { FormatString = "Password is not valid for this user." };
session.Message(
InstallMessage.Error | (InstallMessage)(MessageBoxIcon.Error) | (InstallMessage)MessageBoxButtons.OK,
record
);
Is it actually impossible to show an error message in UI sequence (Immediate execution) using MsiProcessMessage?
Method 2: MessageBox.Show
Using Windows.Forms works for showing a message box. However, message is displayed in background of setup wizard, and shows a separate icon in Windows taskbar.
Is there a way to get window handle of installation wizard, and that way solve this problem?
You didn't quite mention this, but I'm guessing that you are invoking your custom action off a DoAction ControlEvent, published off of something like a button click. Underneath the covers, this is very different from scheduling it in the InstallUISequence. MsiProcessMessage doesn't work from DoAction.
For proper integration with the Windows Installer UI experience, you should avoid using MessageBox.Show (your method 2). Better-integrated options include:
Tweaking a message that can be shown on the dialog from which you invoke this action
Showing a popup message by conditionally invoking a SpawnDialog ControlEvent
Showing an additional wizard panel by conditionally invoking a NewDialog ControlEvent
All three of those involve editing the UI of your project, but differently.
I am using a C# custom action followed by a SpawnAndWait Dialog.
Something Like
PROPERTY WORK_DONE="False"
1.LaunchCustomAction (This does some work and sets WORK_DONE to True)
2.Show SpawnAndWait (Exit when WORK_DONE="True")
Problem,For SpawnAndWait Dialog to Appear, I need to mark my CustomAction as
asynchronous, that is to continue installation without waiting for the custom action to finish. But Whenever I do this, Properties are not getting updated and as a result SpawnAndWait Dialog doesn't get closed automatically.
If I don't mark my Condition as async, The dialog doesn't appear and it waits for the custom action to finish first.
My Requirement is to Show a small popup window that lets the user know that there is a background task going on, Please wait.
Please let me know what am I doing wrong.
I am using C# custom Action via Wix Toolset to build the custom action and AdvancedInstaller to build the installer.
I would highly recommend you (if you are willing to) to write your custom action as an unmanaged custom action written in native C++ and use the MsiSetProperty function to set your property. There are lots of Windows Installer incompatibilities and limitations in what regards its integration with managed custom actions.
If you still need to use a managed C# custom action please try to add your custom action as a custom action with sequence in Advanced Installer if this configuration is suitable for your scenario.
Using a custom managed bootstrapper application, I am unable to get the setup progress to stop when the cancel button is clicked. I pull up a confirmation view with Yes/No options. Once cancellation has been confirmed, the setup rolls back just fine. Or, if declined, it continues along. This was done in accordance with:
Cancel Installation and Rollback using wix burn Bootstrapper UI
I noticed same problem also occurs in the WiX setup kit itself, where you could click cancel and wait, and the setup instead of waiting for user to confirm or decline cancellation, continues along.
So, my question is, how do I pause the progress, until the Cancel command is confirmed (or declined) in the confirmation view?
Update: I am attempting to do this by the following mechanism:
Add a new property called CancelWaiting. If CancelWaiting is true, then in the ProgressViewModel, change the logic such that the <PropertyChangedEventArgs>.Result is set to Result.Suspend. The challenge here is to do multiple command binding. The other way would be to combine the Cancel and CancelWaiting paths into one. Anyway, I'll update this thread once I get this going. If anyone has any other ideas, please do post.
Returning Result.Suspend will instruct the Burn engine to stop the installation as soon as possible and keep the Bundle registered to execute again. That is not likely what you want to do.
If you want to prevent the progress from continuing, then you must have the progress callback method wait and not return. You can either do that by showing the message box from the progress callback method or have the progress callback wait on an event and signal the event after the user makes a choice on the UI thread.
I know this is old, but my approach may help someone else struggling. I faced the same issue where I had to pause the progress of the installation/uninstallation of custom burn wpf app.
So this is how I solved it:
I created a popup a modal window via Window.ShowDialog(), because the gui thread will block until the popup is closed.
When user press exit/cancel you can do something like this:
ModalWindow newWindow = new ModalWindow();
newWindow.ShowDialog();
You can add new Window and call it in this way. That will pause the UI thread till user close or give feedback to ModalWindow.
But if you are looking for other approach, here is a good read
http://deanchalk.com/wpf-modal-controls-via-dispatcherframe-nested-message-pumps/
I'm trying to do a quiet install using a Wix created msi. The thing is that there is absolutely no reporting on how the install has gone, i.e. whether it's succeeded or not.
At the moment, I'm logging everything to a file and checking the file afterwards, I'm just wondering whether there is a better way?
TIA
When you run an msi silently, msiexec will have an exit code. 0 and 3010 is 'good' (3010 means reboot needed ) everything else ( especially 1603 ) is bad.
List of error codes and error messages for Windows Installer processes
I would say this is what quiet install is all about - install quietly. :)
You might want to examine other command line switches starting from /q. This is the excerpt from the article about msiexec.exe:
/qn : Displays no user interface.
/qb : Displays a basic user interface.
/qr : Displays a reduced user interface with a modal dialog box
displayed at the end of the installation.
/qf : Displays the full user interface with a modal dialog box
displayed at the end.
/qn+ : Displays no user interface, except for a modal dialog box
displayed at the end.
/qb+ : Displays a basic user interface with a modal dialog box
displayed at the end.
/qb- : Displays a basic user interface with no modal dialog boxes.
If you only need to make sure it's there after the installation yourself, take a look at the add/remove programs console. If it's been installed, it is there (unless you tell it explicitly not to be).
You have gotten the right answer in terms of the exit codes, but I just want to add that another way to allow more "interactivity" whilst still suppressing most of the MSI GUI is to allow a modal dialog to be displayed at the end of the install. This is achieved by adding /QN+ to the msiexec.exe command line:
C:\Windows\system32\msiexec.exe /I "C:\test.msi" /QN+
This will make the install run silently, but a modal dialog will be show at the end of the setup telling you that the install completed.
There are many options with regards to suppressing parts of the GUI sequence, and the command lines to achieve this are sometimes confusing. Please check my post here for a tool that can help to demystify the command line syntax by auto generating it with a simple, free tool.
I want to create a WIX Installer, during the prerequisites check, I want to see the amount of RAM Installed on the system.If it is less than 1 GB, It should show a Message to the user Indicating that "Amount of RAM on the system is less than the minimum required by this product. Do you still want to proceed with the Installation?"
There are two buttons in the message box shown (Yes and No). If User clicks on Yes, I continue with the Installation, If user clicks on No, I will just show the finish dialog or abort the Installation. How can I achieve this?
Windows Installer sets the system RAM amount in PhysicalMemory property. Usually this property is used as a launch condition which stops the installation and shows a message to the user.
Launch conditions do not allow the user to continue. So if this is not an option, a solution is to use a custom action. Your custom action can check PhysicalMemory and show a custom message box if it's not enough. Based on the user answer, the custom action can then return 0 to continue or 1602 to stop.
Here is a sample condition:
PhysicalMemory >= 1024
A custom action is no needed to implement your requirement. You can author a Windows Installer dialog and insert it between two other dialogs ( for example WelcomeDlg and VerifyReadyDlg ) to be conditionally called based on the PhysicalMemory property.
Here's what the ControlEvents and Conditions would look like for the WelcomeDlg:
SpawnDialog NotEnoughMemoryDlg PhysicalMemory < X
NewDialog VerifyReadyDlg 1
Then you create a dialog that looks like a mesage box and call it NotEnoughMemoryDlg. Have a ControlEvent for the Yes button of EndDialog Return 1. Have a ControlEvent for the No button that says EndDialog Exit 1.
If the system has enough memory it'll skip over the call to the custom dialog. If the system doesn't have enough memory it'll call the dialog. If the user clicks yes it'll return and fall through to the next control event which takes you to VerifyReadyDlg. If the user clicks no, it'll return with a cancel message and invoke the setup completed cancelled dialog.
I don't really do much UI work in WiX ( I mainly use InstallShield but the underlying MSI concepts are the same ) so I can't really give you "do this" code. Especially since I don't know what your current WiX UI code looks like. ( Are you using the WiXUI extension? )
You can follow my instructions to show a non-blocking warning for the operating system. Adapting those instructions to warn about the value of the PhysicalMemory property as mentioned by Cosmin shouldn't be too difficult.