About Shuttledude

Shuttledude · ‎Oct 15, 2015

rguggisberg wrote: ...wonder if there is a way to add a condition somewhere in the IS MSI project to skip that pop up if we are installing via Suite. You might be able to get the suite itself to set a property that could be checked by the msi project ... open the suite project, go to "Behavior and Logic / Events", expand Events, right-click an event (e.g., OnPackagesConfiguring), choose "New Set Property", on the Action tab specify the Property Name and Property Value. An alternate approach would be to open the msi project, create some unique property, skip the pop up if that property is set to some certain value. Then, in the Suite project, select the Package of interest, on the Common tab expand the "Install" operation, and in the "EXE Command Line" supply a command argument that just sets the property (I think the property needs to be in ALL CAPS to make it public, such that it can be set via a command line parameter). Hope this helps!

Shuttledude · ‎Oct 15, 2015

I wound up converting to a basic msi for the projects that absolutely needed some minimal feedback and used a /qb (for "quite basic feedback") command line parameter.

Shuttledude · ‎Jan 03, 2014

The first thing I would try is to search for the old app by looking for its registry keys. If it is found, use a custom action to fully uninstall it in the OnBegin function. Then simply proceed to install the new basic msi app, and set all registry keys in the new basic msi project. To set a key, pick a component (conponents view), expand the component and click on the Registry Data node. Right-click to add new keys, string values, etc.

Shuttledude · ‎Jan 03, 2014

Can billboards be displayed in Suite projects during the product installation? When you install the actual InstallShield 2013 product itself, the InstallationProgress dialog displays a series of billboards. How can I do something similar? And is there any built-in support for displaying a *.swf (flash) animation/movie? Thanks.

Shuttledude · ‎Nov 22, 2013

THANK YOU SO MUCH for this useful and timely information! 🙂 😄

Shuttledude · ‎Nov 22, 2013

Looks like that did the trick! 🙂 Seems to work on a standalone computer (not connecting to our Microsoft Team Foundation Server computer), I will need to do further testing to make sure it works on the "build boxes" too. Question: I would assume the same service pack can be used to update build boxes that have standalone (node-locked) IS2013 licenses (i.e., not a full-up IS2013 gui development). Is that correct? :confused:

Shuttledude · ‎Nov 22, 2013

Currently we use Visual Studio 2012, which allows me to include an InstallShield 2012 Spring or InstallShield 2013 project as part of the VS2012 *.sln file. We are thinking strongly of migrating to Visual Studio 2013. I have installed VS2013 and IS2012 Spring w/SP1 as well as IS2013 Premier onto a test computer. But I cannot get VS2013 to "see" the *.ism project files when I try to include them as part of the VS2013 *.sln solution. So I am wondering if we need to wait for the next version of InstallShield (to be named InstallShield 2014, I assume ;)) before we can move on to Visual Studio 2013. Anyone know for sure?

Shuttledude · ‎Sep 13, 2013

Some ideas on how to fix your issue: (1) create the directory you need under , so that it pre-exists (and will not have to be created). Make sure you create it in the right location (in the Path Variables view you can see where is mapped on your local computer). (2) close InstallShield. Right-click the InstallShield icon and select "Run As Administrator". It may be that you couldn't create the directory because you were not running with admin privileges. Just a guess.

Shuttledude · ‎Jul 15, 2013

It seems this is an old question, the short answer to which is it's not possible with a dynamic link. Here is a link to the same question for IS v10.5, a long time ago: http://community.flexerasoftware.com/showthread.php?144004-self-register-a-few-dlls-that-are-dynamic-links

Shuttledude · ‎Jun 28, 2013

Of course it's easy enough to perform a silent automatic uninstall of an InstallScript MSI project, via setup.exe /s /f1"..path to iss file" And 99% of the time I want this to be silent (invisible). But is it possible to have a fully automated uninstall that still shows the dialogs that appear during the uninstall process? I've tried /uninstall and /x with and without the *.iss file, and have tried passing /v/qb and tried other things too ... googled it and looked on this board. Can't get it to work, but it seems I've done this before many years ago ... and have forgotten how. Anyone know if this is even possible? :confused: Thanks.

Shuttledude · ‎Jun 21, 2013

Just cannot seem to get this to work, so here is the workaround I'm using, if anyone else needs to know how to do this: 1) Do NOT include the *.issuite project as part of the Visual Studio 2012 *.sln; keep them separate. 2) Modify the *.xaml TFS 2012 build template file you're using in the build definition -- add a custom InvokeProcess, which merely uses the IsCmdBld.exe utility. Use the -p command line parameter to point it to the *.issuite project you're building.

Shuttledude · ‎Jun 20, 2013

I have no problem performing a local build (on my computer) of a Visual Studio 2012 solution which has an *.issuite InstallShield 2013 project as one of the solution projects. The install builds just fine, I get the setup.exe and all package folders just as if I'd built with the IS2013 GUI. But when I included the *.issuite into the VS2012 solution, a corresponding *.isproj file was not generated! Is that a bug, or design behavior? The reason I need the *.isproj file (which essentially "bridges" the *.sln and the *.issuite) is that I want to build the VS2012 solution (including the installshield project) on Team Foundation Server 2012. I do this all the time with non-suite projects: insert the *.ism into the *.sln, a file with the *.isproj extension is created and I check that into TFS, kick off a build, everything works great (the install is created). So, is it erroneous behavior that I have encountered, or is it "design behavior" (i.e., IS2013 *.issuite projects are not yet supported by Visual Studio 2012)? Anyone know? :confused:

Shuttledude · ‎Jun 06, 2013

If you log on to the Product and License Center, there is a long list of prerequisites and objects that can be downloaded. I had trouble downloading them from behind my company's firewall however; it's probably best if you download those from your home computer.

Shuttledude · ‎Mar 07, 2013

I have downloaded the redistributables for InstallShield 2012 Spring from the website, and have looked at them in "Custom" install to view which components are in which redistributable package -- but I can't figure out which one has MFC71, CRT71, STL71. Don't see them in Legacy Objects or any of the others? 😞 I'm using the Standalone Build if that makes any difference. Does anyone know which redistributable to use? I don't want to blindly install them all to get just a few megabytes worth of objects/redistributables. Thanks in advance.

Shuttledude · ‎Mar 05, 2013

Christopher, you said "I put an MSBuild Exec element in the .ISPROJ to make all the sources writable." I would really prefer to do that instead of using a modified TFS template! My XML knowledge is weak, could you show me the code for this, or perhaps attach an *.isproj file and point out which block or element does this? Thanks! And while I'm at it ... 😄 ... do you know how to use the *.isproj file to specify the build of multiple InstallShield project releases (e.g., TFS build definition invokes MyProduct.sln, which contains MyInstall.ism, that has 2 releases, Release1 and Release2 -- how to get *.isproj to build both releases).

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Re: Automated but visible uninstall of InstallScriptMSI possible?

Just converted to basic msi

Re: Switching from Installscript installs to Installshield Basic MSI package installs

Billboards in Suite projects

Thanks!

Looks OK so far

Does InstallShield 2013 Premier integrate with Visual Studio 2013?

Re: Merge Module locations

Re: Dynamic file linking + dlls registration

Automated but visible uninstall of InstallScriptMSI possible?

Re: Trying to build .issuite project as part of a Visual Studio 2012 solution (.sln)

Trying to build .issuite project as part of a Visual Studio 2012 solution (.sln)

Re: Merge Modules Download

Which redistributable must I install to get MFC71, CRT71, STL71?

Re: TFS and Automated Build