Software Deployment

In a word, don't. Nested MSIs cause all manner of issues with patches, updates and so on.

Let me guess why *must* it be in an MSI:

- the client is insisting? Educate him
- you're using Group Policy to deploy the package? Extract the MSIs and add them separately to the GP item.
- er, they're the only partially-valid reasons I can think of...

Hey good thing......

But the problem is this is a Dotnetfx35 application which installs all the lower versions with thier service packs. Seperating them will cause so many issues.

Morever we need to install the Dotnetfx35 through Citrix which can deploy only MSIs.

So I wrapped the installation through wise script editor and calling this exe inside an msi,But the problem is it is telling "Windows Installer Service" not available another setup is in progress.

So any solution would be much appreciated.............

Well, IMV, .Net Framework qualifies as a system component and should be part of the build. For post-build machines, I'd say you should let Windows Update take care of it. Then, have your package use AppSearch and LaunchConditions to detect the .Net version that the app requires.

Would like to remind that i need only solution how to call the setup having multiple vendor msi.

Other options are out of scope for me as per my customer........

Please let me know is there any option to do this

Other options are out of scope for me as per my customer........Nonsense. Ask your customer if he'd prefer a package which works and can be upgraded and/or patched or some lash-up which will cause his support group no end of hassle? Can't you see that the sort of package you propose to create is EXACTLY the sort which people here rail against, and about which others post here, looking for ways to work around?

Do it properly, or not at all.

BTW, .Net 3.5 is already an MSI...provided you d/l the full version and not the boot-strap version. It's one of the new incarnations which botches the use of patches instead of transforms. Don't forget to include SP1, too.

i don't think there is nonsense here......

I hope you know that we should respect the cutomer needs.

The customer needs this way..........

If u Know tell me a way...........Otherwise i will find myself..............

Then you need to submit your package to the client heavily qualified wiith caveats, to the effect that you cannot guarantee its upgradability or patch-ability. If the client's happy with that, go ahead.

If u Know tell me a way Wow! You sure know how to sweet-talk a chap, don't you? In WPS, try 'MSI Script/Install MSI From Relative Path'. As I say, v3.5 is already in MSI format so no need to futz with the EXE.

Also, a point I should have made earlier: I can guarantee at least ONE of your clients will tell you (i.e. tell you, not ask...) to NOT deploy .Net F/W on their workstations, thank you very much.

Lastly, I'm sure I read somewhere that MS has some Draconian requirements if you want to distribute it in the way you outline. Still, what do I know...

Hey thanx for the comments............sorry if any of my words are hurting......I am in a gr8 pressure.

I know there are options in the WPS .......there are 3 custom action types which allows to do nested MSI installations............

Also we can use Windows Installer object product installation for installing multiple MSIs........These are all fine and i worked with these.

But here is the problem.........Dotnetfx35 is having dotnet20 dotnet30.On installation it extracts 3 msis with multiple patches in which some of the patches will not get applied properly if we are trying to execute them seperately.........so only trying wrap the EXE directly into an msi......Because the citrix deployment will only allow an MSI for installation.

This is what actucally i want..........Please check.......

Hi Richard,
not quite a happy start into the new year, if you have to produce things that even D. Copperfield would not try... :-(

Things like this can't work because there are only certain areas in the installation progress, where one can execute an other MSI file.
If it comes to silent installs, the only spot, where you could do it, would be the very end of the "InstallExecuteSequence".
See: http://johnmcfadyen.spaces.live.com/blog/cns!9DD01136FC094724!167.entry
However, this might work under XP and earlier systems, but you will have security popups under VISTA.

Patches should be applied to an admin install point, then they are no problem anymore!
Like Ian already suggested: Separate them. Make an install point for .NETfx and apply all the patches.
Then install all that stuff one by one.

Regards, Nick

How about going to Windows Installer version 4.x?
Starting from version 4.0 Windows Installer supports "transaction processing".
Multiple-Package Installations: http://msdn.microsoft.com/en-us/library/bb736322(VS.85).aspx

Kim, EdT on the Altiris WPS forum suggested recently that this isn't really what we think it is. I disagree but I respect Ed's views immensely and so am waiting for my client to provide a Vista build (or an updated XP build with WI 4.5 on it) for me to test. Until I see it for myself (or get some definitive answer from a respected source), I'll reserve judgement.