Release settings are there just for backward compatibility. Prerequisites are the recommended way. ... View more

I just downloaded and installed Team Foundation Server MSSCCI Provider 2010 and all the Source Control functionality works great in the InstallShield IDE. ... View more

The easiest way is to simply copy the content of the SetupPrerequisites folder found under the InstallShield folder from your dev machine to the same location found on your TFS build agent machine. ... View more

From the help library: If you are queuing a build on a 64-bit build machine, ensure that you have configured the build definition for your InstallShield project so that the 32-bit version of MSBuild is used to load the InstallShield.Tasks.dll file (which is a 32-bit file); otherwise, you will encounter a build error informing you that the InstallShield.Tasks.dll file could not be loaded. To select the 32-bit version of MSBuild, click the Process tab of your build definition in Team Explorer. Then, under the Advanced node, find the MSBuild Platform setting, and select x86. Note that if you are using a 32-bit build machine, you can select either Auto or x86 for the MSBuild Platform setting. ... View more

That tab is in File Properties dialog of the Files & Folders view ... View more

what does your custom action look like? Is it just an exe or vbscript? Also, how about specifying the full path to the exe using [System64Folder]? ... View more

tene, VS and TFS 2010 integration will be improved in the next release. Can you private me your e-mail address so I can include you in the upcoming Beta program? ... View more

Look at the CDROM Platforms release property and see if Windows 9.x is set. Also, look in the General Information View and verify that no specific Windows 9.x is specified. Those platforms are not supported anymore and removing them from the project/release setting should fix the error you are seeing. ... View more

I can't reproduce this.... If you click the 'Show Details' toolbar button and look at the File Name field, do they all show the same full path to the msm file? :confused: ... View more

Did you check Crystal Report's support about their merge modules? In the past, we've seen issues with the ways they author them... ... View more

Are you running from inside Visual Studio 2008? Did you try running the InstallShield IDE? Can you provide more details? ... View more

Windows Installer has a limit of 32767 files as this is what the msi database schema defaults to. For Basic Msi, InstallShield uses a modified schema when you have a larger number of files included in your project, but this is not done when building a merge module project. As a workaround, try modifying IsMsiMM.itp in the InstallShield\Support\0409 folder so the Sequence column definition is i4 instead of i2. Also, update the the _Validation table. Here's an MSDN page with more info. http://msdn.microsoft.com/en-us/library/aa367767.aspx ... View more

Are you running on XP? Make sure you install the proper Code Pages from Control Panel | Regional And Language Options | Advanced | Code page conversion tables first. ... View more

You can easily create your own Prerequisite using the Prerequisite Editor (found under the Tools menu). ... View more

You can look at the InstallScript functions XCopyFile and DeleteDir. The help library includes samples. ... View more