About Server

Server · ‎Jun 02, 2011

Try updating InstallShield 2011 with Hotfix A via the automatic update.

Server · ‎May 31, 2011

Don't re-define default strings when Premier multilingual project opened in Professional edition InstallShield with one language.

Server · ‎May 19, 2011

Change to standard W3C xml shema... Some variant of Windows Installer XML?.. Solution for the automated installation testing and unit tesing; Installation Specification export to MS Word, MS Excel from InstallShield and Collaboration.

Server · ‎May 19, 2011

Specify event for these controls depending on your wishes... Event: [PROPERTY_NAME] Argument: YOUR_VALUE Condition: 1

Server · ‎Apr 17, 2011

21. .NET custom actions editor integrated and WIX DTF integration possibility (at least it is only usable .NET custom actions solution).

Server · ‎Apr 10, 2011

13) Comment and/or answer from Flexera Software regarding future development plans for InstallShield product. Communication with developers and participation in this thread. :mad:

Server · ‎Mar 31, 2011

Hello, I would like to start to collect user requirements related to InstallShield 2012 in this thread. Please post your suggestions and proposals. And when it comes to us: 1. Setup.exe supporting multiple product installation (customization of the products to be installed and etc.); 2. Make parts of the InstallShield functionality re-usable and re-distributable from WIX DTF custom actions as .NET libraries; 3. InstallShield Automation interface - provide simple example code in the documentation, how to add components to the InstallShield project and so on. 3. TFS integration should be improved - ready to use TeamBuild automation template(targets?) and examples of the implementation; 4. VisualStudio UI should be faster; 5. Solve licensing headaches with Standalone Build; 6. Lower price ~20% - realistic, but in fact 30-40 needed to follow the market. Maybe step by step. That is what we initially need...

Server · ‎Mar 31, 2011

Good idea... But some wishes might be out of scope and according to my experience Flexera don't usually follow this. Started here: http://community.flexerasoftware.com/showthread.php?t=197183

Server · ‎Mar 30, 2011

It look like same experience in your cases! I also attempted to do the implementation of our custom tool that uses IS automation, but stopped on some point - had other work to do (and also found some features incomplete, but thought that they just poorly documented). And I doubt that customer want to invest in development of the custom tool in addition of such big license expenses. Some conclusions that we made: InstallShield don't improve and release features that customers need; At the short term - bought concurrent licenses in expense of usual ones to improve development experience (but even here had problems with the paid delivery - took ONE MONTH); As the long term plan - minimize usage of InstallShield features as much as possible; Evaluate other MSI design tools and keep WIX DTF as a core technology; Only great functionality that we admire - visual designer that allows fast and easy review of the UI, sequences, components, features and custom actions implemented. So integration with Microsoft and Visual Studio 2010 now doesn't matter - product don't follow market requirements and priced out of the market. Why such non-customer oriented strategy chosen by Flexera? Is InstallShield internal design so poor that it doesn't allow improvements to be implemented fast and with good quality? My proposals: Lower price, then community will support tool and question won't be so siginficant; Implement plugin interface; Re-write product (original one could be even open-sourced) following latest market demands and this will make support price lower. Just ways how to keep market share... It is dare, but it might be good to start the petition or use this topic to somehow get the response from Flexera regarding future plans.

Server · ‎Feb 21, 2011

Are you sure that this is done by installation itself and not any other custom action? Like WCF activation on something like that...

Server · ‎Feb 15, 2011

I also heard about issues with licensing. But with Concurrent licenses. We have very significant delay with the delivery and this is very painful. And now I am worried very much about our standalone builders updates... We don't do any standalone on 2011 currently, only 2009. And if we use licenses included in the old maintenance plan (10) - we also need to order some license files from support? Flexera should do something about it's business processes or it is a way to hell. :mad:

Server · ‎Jan 28, 2011

I also would strongly recommend switching to C# and DTF and don't bother with VB stuff anymore.

Server · ‎Jan 24, 2011

Good day InstallShield developers, I want to create some pool to analyze InstallShield usage practices in the community and share my own experience. It is sad that some of the InstallShield functionality that we payed for is not in the condition when it is usable in the modern world and environments. As result - we pay for the features we actually don't use in InstallShield. Let's localize this ineffectiveness. Let's help Flexera to drive in the customer's direction. So... My list as follows: We don't use in general: 1. Setup.exe because it doesn't allow multi-product setups and functionality is quite limited (will be replaced by custom solution); 2. .NET custom actions because the support and error handling implemented in them are too poor (WIX DTF is free and much more supirior); 3. InstallShield Automation interface - poorly documented from my point of view. 4. InstallShield Collaboration - poor tool functionality and application developers don't want to use it in general; 5. VisualStudio & TFS integration - UI is slow and integration is not complex (causes issues). 6. Technical support - usually useless in Bronze maintenance. Usually faster to solve problem by yourself or bypass the issue in case of the application bug. Most time spend on the assuring technical support that you is not a lamer and problem is serious. Features that have value for us: 1. Visualization of the MSI package design; 2. IIS support and custom actions; 3. WYSIWYG GUI editor; 4. Older InstallScript support (but soon won't be); Your experience?..

Server · ‎Jan 20, 2011

Use LINQ for Windows Installer in DTF - my suggestion. It should help. Of course if you familiar with LINQ itself. 🙂

Server · ‎Jan 18, 2011

Good recommendation for you - forget InstallShield .NET custom actions. Use WIX Deployment Tools Foundation ones. They are MSI DLLs for InstallShield. They have excellent error handling and can include referenced assemblies if they are not in GAC. Personally I have business success with this.

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

Re: Visual Studio 2010 restarts...

Re: InstallShield 2012 wishlist

Re: InstallShield 2012 wishlist

Re: Yes/No dialog for choosing to install a file

Re: InstallShield 2012 wishlist

Re: InstallShield 2012 wishlist

InstallShield 2012 wishlist

Re: InstallShield 2011 features that you paying for but don't use

Re: InstallShield 2011 features that you paying for but don't use

Re: Installation modifies unrelated application pools

Re: Why upgrading to InstallShield 2011 is such a pain.

Re: Populating Combobox with custom action

InstallShield 2011 features that you paying for but don't use

Re: Managed Custom Action

Re: Managed Custom Action

Re: Visual Studio 2010 restarts...

Re: InstallShield 2012 wishlist

Re: InstallShield 2012 wishlist

Re: Yes/No dialog for choosing to install a file

Re: InstallShield 2012 wishlist

Re: InstallShield 2012 wishlist

InstallShield 2012 wishlist

Re: InstallShield 2011 features that you paying for but don't use

Re: InstallShield 2011 features that you paying for but don't use

Re: Installation modifies unrelated application pools