Tech Tips, Application Packaging

Many times I come across articles, where people discuss on which to choose WISE Script or VBScript while creating Custom Action in the package. Here are some advantages and disadvantages of both.

Well this is an intresting tip while moving from XP to Vista. When we launch the Help file in Vista, Help file (.hlp) may give you the following types of errors.

There are many installshield applications (MSI)/ Other Vendor MSI which come wrapped in setup.exe. The packagers can extract the MSI easily, but while installing the MSI, sometimes an error comes which says that the MSI can be installed only through setup.exe.

Some time ago, I put all the ICE errors/solutions into one document. I have collected them over the years, by solving them and getting solutions from colleagues, ex-colleagues, internet sites,(don't remember all the sites, but of course AppDeploy.com and juice.altiris.com are part of it.)

I have learned an easy way of copying condition directly in one Custom Action from other. This is totally from my own experience, and I have not found any material for it on net too. So here it goes...

Properties can be used to select functionality you want to install in MSI.

There are many applications which provide multiple functionalities and we want to choose among those functionalities which are to be installed. So if you are purely packaging an MSI from scratch you can provide deployer with options.

Sometimes you may encounter the problem of unnecessary repairs of MSI while launching the shortcut in the same logged in user. Here is the way to troubleshoot this problem.

Are you looking for a Windows PC just to create and test a layer? There is a free and fast solution to use a machine with Microsoft Windows XP/Vista OS without pay one cent for the Windows license. This solution is supplied by directly by Microsoft.