Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Install whit MSIs


5 replies to this topic

Hatecrew

Hatecrew
  • Full Members
  • 5 posts

Posted 21 August 2008 - 10:09

Hello all,

I've got a very big problem.

I must creat a MSI that includs 5 MSIs. The included MSIs must be startable as silent call.
I use Installshield 2008

Has anyone an idea how to do that?

Best regards
Flex

Edited by Hatecrew, 21 August 2008 - 11:49.


NeilH

NeilH
  • Full Members
  • 3 posts

Posted 23 August 2008 - 17:11

Flex I want to add to your thread if I may, as possibly our solutions are similar....

Netsted MSI's are a no go, so I imagine you would have to chain your installations and thats where I want to jump in.

I want to deploy an application....it has several parts

Server side programs
Client side programs

The client side core application requires .NET Framework 2.0 (Yes I aggree this can be a prerequisite)

The client side install can also offer additional options.
1) Office intergration application but requires VTSO
2) Crystal components for reporting (Can use a merge module)
3) Analytics application - requires pivot table services plus a few others

Not only that but the customer may also install multiple instances of this product (Crystal for example would be common)

I have Installshield 12....the main installation has evolved from very early Installshield versions and therfore has installscript.

Microsoft Certification is important and so are silent installs.

Administrators should also find my components easy to deploy.

I have to consider operating systems from Windows 2000 upwards......

I believe there should be a common interface....one auto run on the CD that launches some thing.....the question comes down to what that something is.

Would I be traveling down the correct road....to build for example a C# front end that asks the customer all the installation questions?

Then perform silent installs of whatever was selected?

How would I get a proper "Progress bar" or can I render the progress bar of each install? (Pivot table serverices for example?)

Where can I find a good example of the above?

or am I going about this all the wrong way?

Regards

Neil

















Hatecrew

Hatecrew
  • Full Members
  • 5 posts

Posted 25 August 2008 - 07:44

Hi Neil,

yes that was also my first idea but that doesn't go, because we had the 5 MSIs and they don't want change it.

They want a MSI that install default all 5 MSIs or custom only the selected. That you doesn't must select all options off the other MSIs they must runable silent whit default parameters.

I use Installshield 2008, and i have many answers that this must be possible, but no one can post me an example.

Greez
Felix

phood

phood
  • Full Members
  • 37 posts

Posted 26 August 2008 - 16:28

I wrapped my MSIs in an InstallScript wrapper. Each MSI represents a feature in the InstallScript project.

I'm not sure this is the best solution, but I didn't want my users dealing with about 20 different installers (including COTS).

Hatecrew

Hatecrew
  • Full Members
  • 5 posts

Posted 28 August 2008 - 08:19

And how have you done?

Can you post an little example or an website that explane that?


phood

phood
  • Full Members
  • 37 posts

Posted 02 September 2008 - 20:17

Hello,

Here is a sample of some code from the Installed event of one feature in my InstallScript project.

CODE

strWorkingDir = TARGETDIR + "\\Installers\\Tcjboss";
strMsi = "\"" + strWorkingDir + "\\JBoss.msi\"";  
strExe = "msiexec";
strArgs = " /i ";
strArgs = strArgs + strMsi;      
if(UPDATEMODE) then
    strArgs = strArgs + " REINSTALLMODE=vomus ";
    strArgs = strArgs + " REINSTALL=all ";
endif;

strArgs = strArgs + " INSTALLDIR=" + TARGETDIR + " ";
strArgs = strArgs + " ADDLOCAL=ALL ALLUSERS=1 ARPSYSTEMCOMPONENT=1 /qr";    

// Run installer
ChangeDirectory(strWorkingDir);
LaunchAppAndWait(strExe, strArgs, LAAW_OPTION_WAIT);


This seems to work for me. Of course, using InstallScript as a wrapper requires that you learn a good deal about InstallScript.

Pat