Assembly: System.Messaging (in system.messaging.dll)
Typically, you do not call the methods of the MessageQueueInstaller from within your code; they are generally called only by the installutil.exe installation utility. The utility automatically calls the Install method during the installation process. Installation is transactional, so if there is a failure of any installation project component during the installation, all the previously installed components are rolled back to their pre-installation states. This is accomplished by calling each component's Rollback method.
After a successful installation of all the components that are associated with the installation project has occurred, the installation utility commits the installations. Commit completes the installation of the MessageQueue by setting the queue to the appropriate initial state. If the queue specified by the Path property already exists and contains messages, Commit clears the messages. Commit, rather than Install, clears the messages because the act of purging the messages cannot be rolled back.
An application's install routine uses the project installer's Installer.Context to automatically maintain information about the components that have already been installed. This state information, which is passed to Commit as the savedState parameter, is continuously updated as the utility commits each MessageQueueInstaller instance. Usually, it is not necessary for your code to explicitly modify this state information. When the queue has been cleared, Commit posts a log entry to the savedState that is associated with the installation.
Windows 98, Windows 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see System Requirements.