http://msmvps.com/blogs/installsite/archive/2009/03/13/answers-from-the-msi-team.aspxLast week at Microsoft’s Global MVP Summit I had the opportunity to sit down with the MSI and WiX teams. It was great to meet all these Windows Installer experts and we had some interesting discussions. With me I had some questions from readers of myenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/installsite/archive/2009/03/13/answers-from-the-msi-team.aspx#1678393Mon, 16 Mar 2009 17:44:30 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1678393stefan<p>Support for VBScript and JScript was in MSI 1.0, long before .NET existed. I guess they wanted to have some scripting support for system administrators which don&#39;t create DLLs. </p> <p>What would you see as the most important advantages that an &quot;official&quot; solution from the MSI team would have over using DTF (assuming that it would be very similar technically)?</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1678393" width="1" height="1">http://msmvps.com/blogs/installsite/archive/2009/03/13/answers-from-the-msi-team.aspx#1678387Mon, 16 Mar 2009 17:28:20 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1678387Wade<p>Their rationalizing why Windows installer doesn&#39;t support managed code custom actions is extremely weak. &nbsp;So, instead of having one way developing managed code custom actions, developers are left to the whims of the installation tool vendors.</p> <p>Why do they support jscript and vbscript custom actions? &nbsp;They should have just stuck with calling DLLs entry points.</p> <p>This is an example where the MSI team is out of touch with issues that developers face when creating installs.</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1678387" width="1" height="1">