Infrequent posts about stuff.
“Joe” commented on an earlier post that the Standalone Build Engine is still available for InstallShield Professional users if you were a registered user of either 10.x or 11.x. More info available in this InstallShield knowledgebase article.
Permalink Comments off
I took some time at work today to give a pretty thorough run through to InstallShield 12 Professional. I have to say: I’m pretty annoyed. The last couple of releases under the new Macrovision brand have really been fairly telling about the focus of the parent company.
In particular with InstallShield 12 is the removal of the stand alone build engine from the Professional edition. Now it’s only available if I spend another $1199.00 to upgrade to the Premier edition. Unfortunately I actually make very good use of the stand alone build engine from InstallShield 11.5, 11, and 10 on several build boxes here at work. It has always been really nice to be able to test the automation scripts on my primary workstation and then port them over to a pure build environment with only a couple of tweaks and not have to worry about purchasing extra licenses for the application.
I suppose the upside is that there is really absolutely nothing except some IDE tweaks and long awaited bug fixes in 12 that really give me any reason to upgrade any of my existing projects. Without the stand along build engine I’m certainly going to be giving some thought to not migrating them at all.
However this is really starting to show a trend in recent InstallShield releases that we in the idustry should really be paying attention to. InstallShield X, while certainly having some flaws, was a really well done release that finally combined the entire sweep of InstallShield installation projects under one big suite of applications. You could build for any platform with pretty much a single app, and it worked. Just over a year later and Macrovision buys out InstallShield. The next release (10.5) is expectedly incremental, but still pretty good.
11 is the first full release under the Macrovision banner, and it’s pretty good. There are some interesting features added (The repository being my favorite. Too bad local repositories are still not entirely functional even in the current version!) and overall it’s a decent release.
Then came 11.5 which should have been just a point release, but somewhat unexpectedly they split up the Windows and Multiplatform camps into two seperate suites again. Those of us who were lucky enough to have a software maintenance plan got both versions but the letter that came along with it started to show that the Macrovision’s respect for it’s customers ended at the depth of their wallets.
Now comes 12, which really has very little in the way of substantial updates and they start to take away features? I think that might settle how badly they want the business of a shop like ours.
You know, WiX has been looking really stable lately and it won’t be a big deal to port some of my smaller InstallScript projects over to it. It will be nice to get some of those into MSI finally as well and there hasn’t been any really good reason to do it before now with InstallShield.
Macrovision released InstallShield 12 this morning, and my download of my maintenance fullfilment copy just finished. I’ve heard there were some big changes for the InstallScript language, hopefully for the better.
Update: I had heard slightly wrong, or at least read the commentary incorrectly. They changed the way that InstallScript custom actions interact with MSI packages. No big changes to InstallScript here…
Permalink Comments off
My name is Nathan Stohlmann and I am a computer geek specializing in software installation technologies and related engineering. I’ve been using InstallShield, Wise, WiX, and various other products to design, build, and maintain scripted and Windows Installer based installation packages for the past 8 years and really think that I’ve found my niche.
I am currently working for Pearson VUE and am relatively happy there but have started to think about what I want to do next.
A note about spam that appears to have come from my domain, cavort.org. It appears that at least one spammer has been using various addresses @cavort.org as the purported sender of the messages. Please believe me when I saw that if I could have that person in this room right now they would leave the room with an extremely funny walk. I do not send spam. This domain has never sent spam. Heck, I’ve never even had a useable outbound SMTP server on this domain. It’s not me and I am terribly sorry if you got crap from that shmuck, but there is absolutely nothing that I can do about it at this point.
No one should be recieving mail from any users @cavort.org. I am the only current user of the domain and am currently only accepting mail to the “nate” and “junk” mailboxes. If you wish to contact me, please use one of those addressess or my gmail account if you know or can derive it.
Permalink Comments off
While InstallShield’s Installscript does not have any String functions that can handle case sensitive comparison, the List functions do!
////////////////////////////////////////////////////////////////////////// // function NRS_StrCompare // Case-sensitive compare of 2 strings. // Returns 0 if the strings match, -1 if they don't. ////////////////////////////////////////////////////////////////////////// function NUMBER NRS_StrCompare ( szStr1 , szStr2 ) NUMBER nReturn , nResult; LIST listList; begin nReturn = -1; listList = ListCreate ( STRINGLIST ); ListAddString ( listList , szStr1 , AFTER ); nResult = ListFindString ( listList , szStr2); ListDestroy ( listList ); if ( nResult == 0 ) then nReturn = 0; endif; return nReturn; end;
Permalink Comments off
