Grrrr

Dammit, comments were supposed to be disabled on that previous post, but they got reenabled at some point while editing the drafts.

Removed for now.

Breaking News

(Update: The error 87 is solved over here.)

Attention everyone. I would just like to take this opportunity to announce that InstallShield still sucks. That’s all, thank you.

Ever since I started on the InstallShield portion of this project I’ve been fighting to get it to cooperate with our source control system, Perforce, which is supposed to integrate nicely with it. No go. Anytime I’d try to add the project to source control it would appear to work, but then after loading the .isv file tables would be missing and the project would be corrupted.

It wasn’t just a problem with Perforce, though. If I directly tried to export the project to text, it would fail partway through with an ‘Error 87: Error in Exporting Table(s)’. Merely going into the Direct Editor and just selecting the ISProductConfigurationInstanceProperty table would also produce an ‘Error 87: Error retrieving primary keys for table…’ Tech support was no help at all; apparently a couple other people have seen the same problem, but there was no solution posted.

Yesterday though, I finally got fed up and moved the whole development environment over to my other system, running XP. I don’t like to use it for development since it’s already bogged down by a bunch of other apps, but I had to try something. And now it apparently works fine on this system.

Curse you InstallShield! *shakes fist*

(Maybe it’s a problem with Windows Server 2003; I’ve also had difficulty with cygwin on there.)