I have seen a sporadic error in my installer where custom actions written in C# exit but the install fails with the 1603 error when the action exits. I put a log message just before the return and it gets logged but the install fails. I checked and there are no objects that need to be disposed. It seems that an action that is scheduled to run the immediate sequence is more prone to failure. It was the most evident during an automated test continually installed and uninstalled the product. It had me thinking it had something to do with garbage collection and continually running. Recently, I saw the problem during an initial installation. Running the install again, worked fine. Are there any known issues or gotchas with managed custom actions? I am currently using 3.5.2430. I need to wait another 6 weeks to move to 3.6 unless someone can tell me a known issue was resolved. I am also building the managed action all for .NET 2. Would I see any difference if I built for .NET 4? This would be a doable change.
I haven't compared a log that functions normally and the one that fails to see if I can find anything. That is next on my list. thanks for any help. -john -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/1603-error-when-a-managed-custom-action-exits-tp6612354p6612354.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
