I hope this is the right spot. I am using InstallShield 11 and I need to know a simple way to create an installation log file. I am using an Installscript project NOT InstallscriptMSI. I can get no help what so ever from InstallShield and it's really starting to tick me off. I now that a .ilg file is created in a hidden folder but it can only be read with the IS log file viewer. That does me no good for somone installing my app and can't read or even find the file. I just want to create a simple text file in the installed directory that a user can view if they run into any problems. Thanx.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
My project was not created with Universall Installer, but with the regular InstallShield 11, so none of those help me. The InstallScript cannot automatically generate a log file. Script has to be written to make it do that. All I need is some pointers in that direction. I cannot change the installation to another type from plain InstallScript because this is the type that upper management wants.
Try...?
Turn off invisibility. Install product. Using explorer, browse first the important directories (application, temp, windows) then the entire drive, for all files, sorted by date (you can filter of creation date, such as, after yesterday). Ensure you have written to logfile (at least a projectname and datestamp)
> a .ilg file is created in a hidden folder
If true, that simplifies the search in windows by file extension. Look at it in notepad
> but it can only be read with the IS log file viewer
?
shame on them. bet ya there's nothing in it worth their reading anyway
You need another form of file you can write to, with your own messages, then it'll be a log. Sorry I dunno the syntax for your version. Just try to create a file, if you have to use dos commands to shell to do that. Including "echo Begin > MyFile.Log" But they should have their own 'nice' way to do things like dos commands and writing to files
http://www.macrovision.com
Log file functions obtain information from and copy information to the custom
logging section of the log file. Custom log file entries do not affect maintenance or
uninstallation of the application unless you add code to the script to read custom
values and perform actions based on those values. The log file functions cannot read
data from or write data to the maintenance/uninstallation
the section where the setup automatically writes data, such as the files that are
installed and the registry entries that are created, and from which it automatically
reads data during maintenance or uninstallation). The following list briefly describes
each log file function.
ListSetIndex Uses an index to set the current element of a list.
ListValid Indicates whether the specified list is valid.
ListValidType Indicates whether the specified list is valid and is of the specified
type.
ListWriteToFile Writes a string list to a file.
Table 10-20: Log File Functions
Function Description
LogReadCustomNumber Reads numeric data from the log file's custom
logging section.
LogReadCustomString Reads string data from the log file's custom
logging section.
LogWriteCustomNumber Writes numeric data to the log file's custom
logging section.
LogWriteCustomString Writes string data to the log file's custom logging
well, you don't have to, some people like to delete their questions instead (my faux pas not knowing the vendor better)
more power to you, and if anything I can advise then it is to consider that more can be better , as well as KISS
I like two logs other than the one in the can. One is a detail that can cover anything that can go wrong. That is too techie for many, better for debug. The other is simple brief text of little more than success/failure, that can have a format to be easily pooled for multiple machines. Also easily viewed and interpreted by user on first call to a helpdesk.
So if you only have one, think of the other.
Thanks, and good look.
Business Accounts
Answer for Membership
by: bjqrnPosted on 2006-02-22 at 13:33:55ID: 16023699
Take a look at this:
http://support.installshie