I was in need of reading data from an .msi file and after reading a nice article in the form of a pdf file, I made a simple console application that takse 2 command line arguments (first is full path to .msi file second one is the table name). I prefered doing a console application because it will be useful to all even having MFC or windows knowledge.
Last week I installed InstallShield for Windows Installer 1.5 on my system and some how I learned how to create an .msi setup file. I was in need of it as we planned to port the tool on which I'm working to the newer version of InstallShield. I searched for help but finally helped myself to learn how to create msi files with InstallShield. I wouldn't say I mastered InstallShield but I can say I know little bit of InstallShield.
Actually the tool for which I have been working on needs the details of .msi files to create MOF files, so I was trying to read the .msi database (.msi is a setup file implemented as a database by Microsoft and it is run by Windows Installer, a service which runs in Windows 2000 and Windows XP).
Using the Code
First location I refered is MSDN. It says what are the functions we have to manipulate a .msi database. But as my attempt to work myself with the MSDN help to read .msi databse didn't work. So I searched on net. and I got nic pdf file regarding this pdf file http://www.wise.com/filelib/MSIwhitepaper.pdf. Please read the article for a full description on "how to". I used the code help from this article only. The flow goes like this. First we have to start with
MsiOpenDatabase(..) which gives a
MSIHANDLE after successful opening of the msi database. Then I called
hDatabase is the handle got from
szSelect is a normal SQL query, then
hView is the
MSIHANDLE returned by this function on success. This function when called creates a view with the given query. To get the actual records we have to call
MsiViewExecute(), which gives the perfectness to the view(means practically this function executes the query and stores the result in the view) Then remaining part of the code is parsing the data and printing on the screen. I once again repeat the pdf I read is the source for my application. I thank "Gary Chirhart" for writing such a nice article on Installer. my application takes 2 command line arguments( other than application name)
- msi file path: rememeber to give the path with "\\" separation like D:\\Share\\VMTNet.msi
- A table name existing in .msi database. There are so many tables but I prefer to give "File" as 2nd parameter.This table contains all the details embedded files in the .msi database.
For better understanding of the database structure one can use "ORCA" tool.
Points of Interest
The interesting thing I learned is actually we don't need any third party tools like Installshield or wise Installer to create .msi setup files. Everything can be done by us The only thing the third party vendors are doing is making things simple so that we can concentrate on development of our software so that we need not worry much about creating installers to our software.