Ah, then you should be posting in the "InstallShield Limited Edition for Visual Studio" forum instead. While there isn't an SP1 for the limited edition at this point, the prq file in question can be shared from the other editions of the product. ... View more

Have you updated to SP1? It contains an updated ReportViewer prerequisite file that addresses this. ... View more

I'd start by taking a look at this thread. There was a problem identified before the release of InstallShield 2015, but it was fixed in the original release. ... View more

Do you have SP1 applied? There's at least one known reactivation issue that was fixed in the service pack. ... View more

Are you expecting to see the square bracket, percent sign, and word 'thread'? Because that's not what this requests. The formatted string pattern [%name] looks up an environment variable named name. In order to request the actual bracket, your string should look like [\[]%thread] instead. Note that it would also be a good idea to escape the square bracket before %property{NDC} as well, but apparently Windows Installer can already tell this isn't such a reference. ... View more

I don't think we can make any guarantees for a moving platform. That said, I do not anticipate that Windows updates or upgrades would break the activation of InstallShield. (If it does, it's likely to break a lot more than just InstallShield, and I'm sure Microsoft will try hard to avoid that.) ... View more

Selecting a radio button typically sets a property. You can then modify the Control Event on the Next button to act differently depending on a condition that involves this property. Take a look at the LicenseAgreement dialog for one example of radio buttons and referencing their properties, although that example uses Control Conditions instead of Control Events to respond to the radio button's property. ... View more

Note that the (for lack of a better term) pseudo-property must include the final term as actionState not just action: FEATURE[feature-name].actionState. The notation FEATURE[feature-name].actionState is only available to actions run by the UI, so of the kinds you mention, you will need a C++ DLL that uses the ISuiteUIExtension interface to read and set properties. As our managed code and InstallScript actions are run by the engine instead of the UI, they will not have access to this pseudo-property. In C++ the syntax will look something like the following, depending on the name for your variables, and what (if any) helper classes you use: [CODE]spSuiteExtension->put_Property(CComBSTR(L"FEATURE[feature-name].actionState"), CComBSTR(L"install"));[/CODE] See Referring to Feature States and Other Feature Data in the UI of an Advanced UI or Suite/Advanced UI Project in the help, as well as the help topics near it, for related information. ... View more

It's really hard for me to answer in the abstract, but I've not heard of it being common to edit the .targets file. (If that does appear to be the solution, and there's some tweak we could make to the standard issue .targets file to make future edits possible in the .isproj file alone, let me know.) In a more general sense, it's completely possible to modify paths or values, but I'm not sure what to recommend here. If you're using project outputs, I know there has also been some disparity between "obj" paths and "bin" paths; building in Visual Studio provides one for project outputs, and building in MSBuild provides another, at least in some versions of Visual Studio and/or MSBuild. If you're using static paths, you may be able to tweak path variables through the overrides exposed (either in IsCmdBld or to MSBuild), but I'm not sure how to condition that without, say, a separate build step. ... View more

If you need to access HKCU, the simplest answer is to ensure that your action has its In-Script Execution set to something that doesn't include "System Context" such as just "Deferred Execution". If there are other reasons this action needs to be executed in the system context, you need to find another way to find the correct registry keys for the "current user" you have in mind, such as by locating the correct user under HKU. (Be careful not to over-generalize the HKU approach, as not all user-specific registry data is always available in multi-user systems.) ... View more

Does it have something to do with the state of your project then? I tried in a fairly empty project, although it already had a package in it when I started. If we can isolate the minimal steps to reproduce this, I may be able to find a workaround or fix for you. Can you make the changes in the other order? Can you make the changes in a second project, and then carefully copy the XML from one .issuite to another? To be fair, E_NOINTERFACE is more likely to represent a problem in the state of the product than one in the project. It's possible that running a repair may help. ... View more

Hmm. I'm not up to date on good references for MSBuild; you've already been through the reference on MSDN? I'd probably suggest adding tasks to see what values of things are actually being used, but that doesn't bring you closer to solving your actual problem. On my earlier read I missed that this was being invoked from Visual Studio, and that may be resolving the value passed on the command line. However if that's the case and your path can include spaces, take care to put quotes around it. (I don't think the symptom matches that potential problem, though.) If you're trying to use values from within the MSBuild file, perhaps you could approach it by providing defaults for when the property isn't specified on the command line. We do something similar in our targets file: ... You could follow this approach by using the properties you want and replacing ... with your property reference. ... View more

I wasn't able to reproduce the problem with predefined pages with an arbitrary guess - I was able to remove the LicenseAgreement page and add a BrowseForFolder page without difficulty. Could you mention which page you deleted, and which page you tried to add (if it gets that far)? As for the second, it sounds like browsing for another file named EULA.rtf may not be replacing the Language Independent support file already present. The fix is easy - go to the Support Files view and remove EULA.rtf there, and optionally add your replacement. If you deal with multiple languages, you may prefer to put its replacements in specific language nodes. ... View more

It means we have tested our run-time support for the new operating system, and typically it also means we have made it easy to specify whether your product supports the new operating system. However nothing InstallShield does can ensure your application will or will not work on a different version of Windows than you have verified. The problems are rare for most applications, as Microsoft works hard to ensure compatibility, but they do occur. ... View more

InstallShield supports side-by-side installations of its major versions, so that should be fine. By contrast, service packs are in-place updates so you cannot have both RTM and SP1 of a single major release without using multiple machines (or VMs). ... View more