I'm evaluating Advanced installer for use in our current project. Overall it seems like a great no-nonsense solution.
I have two questions:
First, I've built an install to kick the tires. Worked fine, but there is an issue with the text on the dialog. It seems the label isn't wrapping as I expected.
The select installation folder dialog text and the Ready to Install dialog, both have their text labels cut off with periods of elipses.
For example: Click Install to begin your installation. If you want to review or change any of your inst...
The platform is XP with font size as normal.
How can I fix this?
Second, I'm interested in using Advanced installer as part of our automated build process. Where can I get complete documentation of the command line commands options? The docs only mention the /version command but I see exmaples in the forums of other options.
I expected that the text controls in question had nowrap turned on, but looking at (orca) template.msi I discovered that they just didn't have enough height to accomodate when wrapping. I changed the height in the template.msi rebuilt and it looks fine now.
Do you discourage or encourage editing the template.msi?
The only command implemented currently is /version actually. We want to add more, but we would like to know what functionality people would like to see exposed in the command line interface.
You can edit template.msi as you wish, just make sure you note the changes somewhere and you apply them again when new versions of AdvInst come up.
In time, our target is to expose all the MSI functionality in the UI - while keeping the product easy to use and understand.
Send us a screenshot with the truncated text to support at advanced installer dot com please.
After some comparing with other machines, it was an issue with my own machine. I don't remember adjusting the font size, but after reseting to original theme the problem cleared up. So it was my goof. Learned a lot about your app in the process though. I'm really enjoying it. (In fact, we bought it today)
I can see a lot of potential benefit from opening up the command line. I am using it as part of our automated build (nant). Clearly, version is the most important thing and I'm glad that's what you've implemented.
It might also be nice to be able to set the output file name, or redirect a synchronized directory (our automated build uses version information in the output directory, so now I copy everything to a package directory for building the msi).
Although I haven't tried it yet, it seems rather easy to just update the XML file before building.
I would advise agains updating the XML file directly. There are a lot of rules and interdependencies between various MSI elements, and the logic to create valid MSIs is one of the biggest areas of the AdvInst application.
You are much better using pre/post processing actions (like renaming output file) and letting us know if you need more commands exposed from the command line.
Hello again,
I've spent the last weeks working on getting AI integrated in with our continuous integration process. Overall, it's been very successful.
I do have a couple of suggestions.
First, when run from a command line AdvancedInstaller will display a dialog box when it encounters errors. This is a problem when running in a build process that runs as a service. The end result is that AdvancedInstaller remains open until the process is killed or the dialog box is closed (if interact with desktop is enabled). In my case, either option is a showstopper.
A silent command line option would be great.
An even BETTER solution (for me) would be an option to output status and error messages to an XML log file similar to the output from other tools like NUnit, or NCover that will allow easy integration into our build reports.
(I'm using CruiseControl.NET for CI)
My other suggestion stems from the reason I went looking for an alternate installer in the first place. The installer packaged with Visual Studio .NET is inadequate for all but the simplest of installs, and useless for automated builds (no directory synchronization), and the other installer packages are far too expensive and cumbersome to be justifiable for average install tasks. Advanced Installer is lightweight, nicely in the middle and covers the basics very well, anything else I can handle with custom actions. The way things are now, my only option to use .NET assemblies for custom actions is to use a windows or console exe. What would be really snazzy here (IMHO) is for AI to define an .NET interface that developers could implement in a .NET libray assembly so the installer could call by reflection. We are accomplishing this now by using a simple .exe that will, given an installed assembly name, reflect the assembly, calling implementors of a particular interface (ICustomAction for example) passing in all of it's parameters.
This is the one thing that the VS.NET installer does, that I miss. It may even be possible to use the same interface as the .NET installer classes, although personally I'm not fond of it and since there are Installer contexts and other things that are supposed to exist at runtime, it's probably not a very practical option anyway.
Another benefit of this approach is that not everyone need deal with the particulars of MSI's and custom actions. Anyone can quickly write an implementatin of ICustomAction with very little knowledge at all about MSI's or even AdvancedInstaller. So I only need one or two developers that are very familiar with the tool. I can also easily build and test a custom action via unit tests. It's much more clumsy, if not impossible, with exe's.
If you're interested, I'd be happy to share my experiences and code examples.
That's an excellent point about the framework needing to be installed. Our apps generally require it, so the framework is a prerequisite in our installs.
That reminds me, is there a way stop the install when a required file is not installed, without specifying an exact size for a download? For third-party requirements it is sometimes difficult to link directly to a download (either physically or legally)
(Also, if this information is already in the forum, please just point me, I'm still reading through it all!)
Thanks for being so responsive in your forum. It's appreciated.
Yes, using the EXE will make Advanced Installer show dialogs when running the commands. The COM file is the one which implements the command line interface and it should be used instead of the EXE.
As I'm using Advanced Installer 10.9.1 professional build 55086 and I'm still seeing the same problem.
In that the text isn't wrapping and we are seeing the '...'
FOLLOW US
Get the latest news in Application Packaging