IA evaluation

For all your non-technical questions.
Post Reply
jweksej
Posts: 93
Joined: Wed Sep 27, 2006 4:54 am

IA evaluation

Post by jweksej »

Hi,
I'm really interested in opinion of people who moved from InstallShield or Wise to IA, who do complicated installers for bundle of products/modules. What they think when after beeing IS/W masters they are now IA master. What are IA strenghts and weaknesses. What kind of problems they reached. How helpful was IA support, etc. Just heart-felt opinions of professionals not related to IA, which will help me to make good decision. IA is now on top of my ranking but I need proofs to be not badly surprised in future :-)
MortSkil
Posts: 59
Joined: Mon Oct 30, 2006 3:27 am
Location: Trondheim, Norway

IA evaluation

Post by MortSkil »

Hi,

I share your interests. Have been working with Wise for Windows Installer v6.2 for about a year.

I struggled really hard to create my first full-featured install with WfWI, after first dismissing IS Express.

Maintaining my WfWI project has been OK, and the quality of WfWI forums is brilliant.

However, I am worried about the technical support of Wise through Altiris, as they have not released a single patch since february, and there is no sign whatsoever what they plan to support in the planned release of WfWI 7.

My main concern is that they do not support installing .NET framework 1.1 assemblies on .NET 2.0 target machines. This is actually the reason why I have now ordered IA Studio.

The first issue I ran into with IA is that I did not find support for creating firewall exceptions for installed applications. This works perfectly in WfWI.

I plan to transfer my installation step by step, and if I find any more issues, I will try to remember posting comments in this thread :D .

-Morten
Tinus
Posts: 209
Joined: Tue Jun 20, 2006 8:42 am
Location: Germany

Re: IA evaluation

Post by Tinus »

MortSkil wrote: The first issue I ran into with IA is that I did not find support for creating firewall exceptions for installed applications.
Try it this way:

Code: Select all

Run Program $WINSYSDIR$\\netsh.exe firewall add port protocol=TCP port=12345 name="bla bla" profile=ALL (WAIT)
Martin Rothschink

AxoNet Software GmbH
http://www.axonet.de/products/other-pro ... stallaware
Post Reply