Advanced Installer
more / weitere

InstallShield und AdminStudio Schulungen

weitere Infos

InstallShield Tools & Tips: Debugging

Note regarding InstallShield 6: Unless otherwise stated the tips and tricks on this page have been written for InstallShield 5, and not all of them will work with InstallShield 6. Some may even damage your project files, so remember to make backups first.

Debugging an Uninstall DLL from Visual C++

Here are steps I used to successfully debug an InstallShield uninstall DLL from within Microsoft's Visual C++ 5.0.  For the sake of this discussion, my uninstall DLL is called UninstCPL.dll.

#ifdef _DEBUG
        _asm    int    3
-f"<full path to uninst.isu>" -c"<full path to installed UninstCPL.dll>"

Written by Charlie Rundles

See also: DLL Testing Tool to test the UninstInitialize() and UninstUnInitialize() functions of your DLL independent of a setup project.

Decompiler for InstallScript

I haven't tested it, but this tool says it can decompile .inx scripts created with InstallShield 6 or 7 and additionally allows the user to take a few changes to the code and patch the script.

WWW SID project at GitHub

DLL Testing Tool

This tool lets you easily:

ZIP (133.214 Bytes)    Provided by Eric Olson


RegDrop is a component registration utility that allows you to simply drag and drop a component on it and RegDrop will register or unregister the component for you. This process is much easier than having to locate the REGSVR32 console application to register components. And more important, RegDrop gives real error messages as opposed to cryptic numeric result codes. This is very helpful in debugging self-registration problems in the files you are installing.

WWW Visit Addison Software to download the free RegDrop utility

Send Trace Messages to a Debugger

InstallShield doesn't have a feature like TRACE in C++. Here is a trace function that you can sprinkle in your script code - it will send debug messages through the OutputDebugString Windows API. Use a tool like DebugView to catch and display these messages.

To use the Trace function, include Trace.h at the top of Setup.rul and Trace.rul at the end of Setup.rul. You need to deine _DEBUG in Build ->Settings-> Compile -> Preprocessor Defines. Also it is suggested that you add code like the following to your script, so that you will not distribute a debug version to clients, as it's a bit slow.

#ifdef _DEBUG

ZIP   Written by Satya Gadepalli
File size: 1.208 bytes   Last update: 2000-11-27




English News Discussions Windows Installer Related Tools More Help InstallScript About InstallSite Shop Site Search
deutsch Neuigkeiten Diskussionsgruppen Windows Installer MSI FAQ Artikel     Shop Suche

Copyright © by InstallSite Stefan Krueger. All rights reserved. Legal information.
Impressum/Imprint Datenschutzerklärung/Privacy Policy
By using this site you agree to the license agreement. Webmaster contact