As you could well imagine, with a field as large as application packaging and deployment there are millions of things to do, and even more ways of actually doing it.

Tips and Tricks can make your life a lot easier.


So I was asked to make a small tweak to an application that had already been packaged, looking at the application just with a bit of care, it was apparent there was a lot of Java stuff in the package;

So a new manual install was necessary, it was pretty easy to see one of the dialogue boxes 'installing MS virtual machine for Java'

So the lesson here in the simplest terms is:
“Pay attention to the manual installation process”

Don't just walk away and get a coffee, this is related more to the art of packaging than the science.
So the way to work around this specific problem.

Install the MS Java machine package first, and with any luck the set up will detect it and not reinstall,

Alas, there is no clever logic in the package and it reinstalled the MS JVM again, .....

Try renaming the folder that has the source for the MS Java machine, and say a small prayer, with any luck the installation mechanism will say, I can't find it, carrying on anyway in a graceful manner.

I tried this, and it didn't. work, a big red X appeared, saying fatal error, installation terminating.

So, nowhere near as tidy but this could work:
Install the MS JVM first then do the before capture, then install the new set up and hope that it wont capture the MS JVM, (as it is already there)

This seemed to work so I now have a package with out loads of Java stuff in it. YAY

Tips and Tricks
Will be regularly updated. If you are in a rush and want a new tip now, please E-mail us and will send you a tip.

If you have a particular quandary, tell us what it is and we will endeavour to help you.

Do you have a process?

Is it clearly defined, does the output result in a package that conforms to your standards.

A chicken and egg situation, you need both, standards and a process.
They are separate and should complement each other, NOT conflict with each other.

Tip One:
Have a process.
Follow that process!
Most things that don’t work or have some sort of issue is down to someone skipping a stage, or abbreviating it (taking shortcuts).
When things are left to interpretation they can be misinterpreted, create standards NOT guidelines. Accept that there will be exceptions to the standards. Plan in the early stages an approach to handle these exceptions
Ensure all the stages in the process are completed, and a document output defines the result of each stage. These again must be clear and concise.

 Home About Us Services Tips Aesops

Copyright © 2005 by Three Point Enterprises Ltd. All rights reserved.