I solved this issue by manually saving the properties to [SETUPSUPPORTDIR] and then restoring them. However I think that this should be done by the Suite. ... View more

Thank you for the suggestion. The feature state properties are not working in all suite actions. I've tried to create simple SetProperty Action in the UI and the result was the same. I wonder why is that. In the C++ custom actions that were introduced in IS 2012 it is working correctly. DLee65 wrote: Have you added a reference to the library file in your code? That is the only thing that I can think of. For our C++ custom action I had to #import \SetupSuite.exe #import "..\..\..\Redist\Language Independent\i386\SetupSuite.exe" no_namespace raw_interfaces_only named_guids ... HRESULT __stdcall MyCustomAction(IDispatch *pAction); { BSTR upgradeCode = ::SysAllocStringLen(NULL, 2*iGUID); BSTR bstrUpgradeCode(_T("UPGRADE_PROPERTY")); // Create a smart pointer to the IsSuiteExtension COM interface CComQIPtr spSuiteExtension = pAction; CComQIPtr spSuiteExtension2 = pAction; try { hRet = SpSuiteExtention->get_Property(bstrUpgradeCode, &upgradeCode); }... } Ooops, my bad. I just realized that you are working with managed code and wanted to eliminate the C++ code. http://helpnet.flexerasoftware.com/installshield21helplib/helplibrary/SteActionManagedCd.htm I have not used the managed code only InstallScript and C++. Sorry. The above documents the process though. Unfortunately the documentation seems to indicate that objects for feature state are not exposed. ... View more

Anyone knows how to acces properties like "FEATURE[FeatureName].actionState" from the suite actions? It is just not working for me and I have to use the old C++ CustomActions that I wanted to get rid off. ... View more

Please, noone knows how to make the progressbar in the taskbark working? I am still strugling with this. ... View more

Hello, Could you please specify what exactly is not working? Your approach seems to be correct. ... View more

Thank you for your reply. I only needed ISuiteExtension so I added hidden feature with custom detection as described here: http://helpnet.flexerasoftware.com/installshield19helplib/helplibrary/SteExtCondAuthor.htm#BuildingConditionalStatements_547774590_1039129 I hope it will work fine. ... View more

Hi, there are more ways to register com in IS. They've recently created whitepaper on this topic http://blogs.flexerasoftware.com/installtalk/2013/07/a-word-about-seemingly-hung-com-extraction-processes-by-josh-stechnij-senior-software-engineer-com-extraction-was-originally.html ... View more

TsungH wrote: Alternatively, one can set msidbUpgradeAttributesMigrateFeatures in Attributes column in Upgrade Table. This is also a solution for standard msi upgrade. But you cannot map the msi features to Suite features with only this set. Thank you for your reply. ... View more

The solution was quite easy after all but for someone who is not experienced c++ programmer it can be tough. I created suite custom action where I detect which msi features are installed and set the suite feature action state accordingly. It looks like: [CODE] __declspec(dllexport) HRESULT __stdcall DetectUpgradePreviousInstalledFeatures(IDispatch *pDispSuiteUIExtension) { CComQIPtr spSuiteUIExtenstion = pDispSuiteUIExtension; wchar_t productCode[255]; if(MsiEnumRelatedProducts(L"{MSIUPGRADECODEGUIDINBRACKETS}", 0, 0, productCode) == 0){ INSTALLSTATE featureState = MsiQueryFeatureState(productCode, L"FeatureName"); spSuiteUIExtenstion->put_Property(CComBSTR(L"FEATURE[FeatureName].actionState"), featureState == 3 ? CComBSTR(L"install") : CComBSTR(L"")); } return S_OK; } [/CODE] Of course there is need to add msi.h headder and add msi.lib to linker. ... View more