View Full Version : .ism file is ascii or binary??

08-05-2004, 04:54 PM
I found I need to save this puppy (projectname.ism) into source
control or my project won't be saved (into source control)
correctly. Is it an ascii or binary file??

The strange thing is that the help file says .ism don't get save to
source control. To me they seem to be needed. For example,
I modified (in setup design) a component by deleting a file under
'Files' in setup design and click save. The only file modified by
this action is project.ism file which isn't saved to source control.
So, anyone else opening the .isv file via source control will not
see the changes I made. This is strange, why would InstallShield
not save this file to source control when it is clearly needed.....
OR.....am I missing a step somewhere?????



08-06-2004, 07:32 AM
ISM files are actually msi files. These can be edited with Orca, which comes in handy sometimes.

As for source controling your project, you need to export your ism. This will create an isv and a bunch of idt files. These are what you check in, not the ism file. Once your project is checked in, delete the ism file. The next time you want to open it, just open the isv file, the IDE will convert this back to ism format. When you are done working on the ism, repeat these steps.

You can do all of the above either with the automation layer or through the IDE on the Project|Source Control menu.


08-06-2004, 09:56 AM
Thanks for the response!! After opening the .isv project file
and making changes, I used File,Exort to Text File to update
the .isv and so far everything looks good. Is that it or are
there additional steps I need to take?? Thanks again!!!:)

08-06-2004, 10:11 AM
No that is it. Just one thing to remember is that all of the idt files have to be checked out when exporting the project.


08-06-2004, 01:02 PM
Yepper, I'm using wincvs to save items into our cvs repository
on linux. It works just fine:

1) Checkout the latest version of the project
2) Using installshield, open only the .isv project file and make changes.
3) When complete, run file,export to text file to update .isv and .idt files.
4) Using wincvs I do a 'cvs diff' on the isv and all .idt files to determine
which ones have changed. Changed files get committed back into the source repository.
5) Delete .ism file in the same folder as the .isv.
6) All done...Miller Time!!!

Thanks again Anthony...


Christopher Painter
08-06-2004, 01:29 PM
You may want to consider upgrading to DevStudio 9. 9 allows you to save the ISM in XML format which greatly simplifies the version control process.

If you want to stay with an .isv/.idt system, I can provide you with a VBS code snipet that can be used to rebuild the .ISM.

08-06-2004, 02:25 PM

That's good to know. Currently, my company is running on
a shoe string so I don't think we'll be updating to the latest
version. The .ism file seems to rebuild anytime I open up
the .isv file so I don't think I need the VBS code, but thanks
for the offer.