floort Absent Member.
Absent Member.
1996 views

Installshield, Basic MSI or installshieldscript

Hello,

I'm normally use Wise package studio to create normal windows msi packages.
Now we have to pay for upgrade to support windows 2008 operating system.

I trying to get some feeling with installshield because that's free for us (in combination with zcm).
But how can i see that i'm creating a normal basic msi instead of a installshieldscript msi.
Is it true that i need to deploy extra things (installshield engines) before i can deploy installshieldscript msi's?, and why shall i choose for that one.

I try to get my way into the lot of windows inside installshield / adminstudio.
(WPS was much easier, but there is less development on it)

I hope someone can explain me a bit.
Labels (2)
0 Likes
2 Replies
Micro Focus Expert
Micro Focus Expert

Re: Installshield, Basic MSI or installshieldscript

If the result is an MSI it's an MSI.

If the result is an EXE, it may be dependent on some of the
InstallShield Script stuff. (At least that is my understanding.)

If you find yourself having issues, you could just make a habit of
forcing out the latest InstallShieldScript.msi to devices so its there
if needed.

There is nothing really unique about the version of AdminStudio that
ships with ZCM. You may find more detailed answers about using the
product on their support forums, but they honestly seem to be a bit
lacking. Appdepoy.com is another good site that covers some of this stuff.

You may find ppl in this forum that can answer some of those detailed
questions, but generally the questions tend to be more ZEN specific.


On 9/24/2010 6:06 PM, floort wrote:
>
> Hello,
>
> I'm normally use Wise package studio to create normal windows msi
> packages.
> Now we have to pay for upgrade to support windows 2008 operating
> system.
>
> I trying to get some feeling with installshield because that's free for
> us (in combination with zcm).
> But how can i see that i'm creating a normal basic msi instead of a
> installshieldscript msi.
> Is it true that i need to deploy extra things (installshield engines)
> before i can deploy installshieldscript msi's?, and why shall i choose
> for that one.
>
> I try to get my way into the lot of windows inside installshield /
> adminstudio.
> (WPS was much easier, but there is less development on it)
>
> I hope someone can explain me a bit.
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
0 Likes
dandirk Absent Member.
Absent Member.

Re: Installshield, Basic MSI or installshieldscript

For quite a while installshield has been moving away from installscript... They have only just recently added features to better edit/support installscript installs. If you are snapping/monitoring apps an creating msi's they will all be pure msi. If you are editing, then you could run into some installscript stuff.

Yes you will run into apps that require installscript engine (probably not ones you build). There are a number of different versions etc. Though I see less and less recently. Every time we run into one, we create separate bundle and call it with an install bundle action. We pretty much are at the point where we don't run into any new versions and can just reuse the bundles (as install bundle actions) we already have.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.