Differences in Pro and Ent. versions

Got a problem you cannot solve? Try here.
Ishana
Posts: 11
Joined: Sun Dec 05, 2004 6:25 pm
Location: Omaha, Nebraska
Contact:

Differences in Pro and Ent. versions

Postby Ishana » Mon Dec 06, 2004 3:07 pm

I am trying to decide on between Professional and Enterprise versions.
Can someone please explain what these are and where they can be used?

These are the factors that I didn’t understand from the two versions listed above.

If there was direct links to each of these, I wouldn’t be asking. I know the guys at mimar are probably busy and don’t have time to create a product matrix that explains every such detail so I am asking here.

Service Support - Is this InstallAware product support?
Database Support - Is this for applications that use DB’s?
Compiler Directives - ?
Manual ICE Validation - ?
Automation Interface - Where and how would I need to use this?
Web Applications - ?
Redistributable Build Interface - ?
Web Based Automation Interface - ?
Thanks
Ishan

sinan
Site Admin
Posts: 1020
Joined: Sat Nov 13, 2004 8:12 am
Contact:

Postby sinan » Mon Dec 06, 2004 6:11 pm

Hi Again,

Service Support: Installing and configuring Windows NT/2000/XP/2003 services.

Database Support: Installing and configuring ODBC data sources and drivers.

Compiler Directives: They are like IFDEF statements for your installation script. You can customize your setup at build time (either from the IDE or the command line) using compiler variables. This helps you create multiple different setups (say, different product flavors/editions) from a single installation script. For example, InstallAWARE Pro/Enterprise have the same setup script. And compiler variables are used at build time to include/exclude the Enterprise files based on the version being built.

Manual ICE Validation: A stand-alone tool to validate your MSI databases against the XP/2000 logo requirements.

Automation Interface: This is a way to create setup scripts from an external program (outside the IA IDE). You would essentially "emit" a setup script from your own EXE and then build it. Most authors have no need for this. But its useful for creating customized installers from webpages, etc...

Web Applications: Helps you install files directly into IIS folders.

Redistributable Build Interface: The license lets you distribute IA components so you can build your installs on end-user systems without purchasing additional IA licenses for those systems. Again, something most users don't have much need for.

Web Based Automation Interface: Lets you call the automation interface from a web page through a COM object.

Please let me know if you have more questions. If you describe the type of application you plan to install, I might be able to suggest a version for you as well.


Return to “Technical Support”

Who is online

Users browsing this forum: No registered users and 39 guests