Please tell me what are the best practices for(setup capture) inclusion and exclusion on the Wise studio 3.2 like what is must to do and what is best to do both Inclusion screen and exclusion screen in all fields Files, Reg, ini, and shortcuts.

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


For the most part, what you leave in and what you exclude will differ greatly depending upon the package you are creating and the items that are not obvious are generally left in (but at the potential to cause trouble). Trial/error/experience will help you to learn in your lab environment- hopefully before you deploy it to any users.

One solution (the only I am aware of) you should consider is PackageCleaner. This tool scans your MSI and tells you what items you may want to take out- and why. It is like hitting your package with an exclusion list after it is built, the difference being that it tells you quite a bit about each item and why it may cause you problems. http://www.packagecleaner.com

The bottom line is this is not a black and white process and leaving something in can really cause problems down the road when it comes time for an upgrade or remove the package. If you were to perform the same actions in each repackager available you would end up with just as many different packages- even the vendors that make the tools do not provide the same exclusion lists in their products.

Hope this helps,
Answered 03/03/2004 by: bkelly
Red Belt

Please log in to comment
I used to trust WPS to exclude and include the right stuff but decided to have a Plan B just in case and it has worked out a number of times and saved me lots of headaches.

After I capture a setup, I recapture it using Winstall. Winstall captures everything raw (it sometimes misses ini files tho....so beware). It puts the file structure into folders and also captures the registry changes to a file that you can refer to or import into WPS.

You might never have to use it, but at least if you get stuck you can refer to it and it might provide the clue to the missing link so to speak.
Answered 03/07/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment