I managed to solve the problem by using dynamic file linking. I.e. I deleted the components (project documentation output) pointing to the XML files and added one component that uses dynamic file linking. I then specified which files to include (the XML files) and I was able build my project without problems. I hope this won't come back and bite me in the ***embly in the future. It's been nothing but problems since day one with InstallShield... I hope someone struggling with this same issue will find my resolution useful. ... View more

Johannes John wrote: Hello ppsmxion, I've currently not read the limitations of the Evaluation Version. How large is that XML file. Do you allready have tried a small XML file? Regards Johannes XML file size is 1.52 MB. I was forced to purchase the Pro version so that I have tools to release versions to customers but I still get this same error. I left the xml files out so that I could build an installer but naturally I've started to get complaints about missing class descriptions etc... I haven't tried with smaller files. Are you saying that there are file size limits for xml files? ... View more

Flexera has confirmed that this is a bug in InstallShield 2014 so problem "kinda" solved. Just waiting for the bug fix... ... View more

I got it working using scripts. I.e. I check the state of each feature and send the states to my custom action using custom action of type 51 and CustomActionData. No need for specifying additional custom action conditions because I do all necessary checking in my custom action method. Don't know if this is a bug or conditions are not fully supported in installscript project or I just don't know how to use them. At least, it works this way. ... View more

Just tried the "Dynamic File Linking" feature and this is probably designed for filtering files since it has a filtering option. However, you cannot apply this directly to source output item because it will create duplicates. I.e. if I add source output item and then add dynamic file linking to it with excluded files, it still adds the files originally in source output item. On the other hand, I can create my own components that include certain files (i.e. *.cs etc.) but then I lose the idea of the source output which automatically includes other files (resource files etc.) too. This is a very laborious way to handle this whole thing. It would be great if you could apply this dynamic file linking to source output item and it would filter the excluded files I define. Even better would be if source output item would automatically contain a dynamic file linking object (containing all source related files) which you can edit - and exclude/include files you want. InstallShield has many great features and that's why we have switched to using it instead of that crappy Visual Studio's setup project. However, lag of easy filtering makes VS's setup project superior in this case. I hope you Flexera guys will implement this "easy filtering" too. It would make many people's life easier - at least mine... ppsmxion wrote: How can I filter certain files when I add source output to my IS project (Files and Folders)? Let's say I want all my .cs (C# files) files in the installer but don't want .csproj (C# project file) file. I have just switched from Visual Studio's (2010) Setup project to InstallShield and I'm trying to create an identical installer. I just can't find a way to filter files like in Visual Studio's Setup project where you just right-clicked source output item and applied an "ExcludeFilter" (where you define using wildcards which files you want to filter out). ... View more