<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://weblogs.asp.net/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Adrian Alonso's blog : WIX</title><link>http://weblogs.asp.net/adalon/archive/tags/WIX/default.aspx</link><description>Tags: WIX</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP1 (Build: 20510.895)</generator><item><title>TCI - Toolbox Controls Installer</title><link>http://weblogs.asp.net/adalon/archive/2007/09/07/tci-toolbox-controls-installer.aspx</link><pubDate>Fri, 07 Sep 2007 17:35:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:3780964</guid><dc:creator>adalon</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://weblogs.asp.net/adalon/rsscomments.aspx?PostID=3780964</wfw:commentRss><comments>http://weblogs.asp.net/adalon/archive/2007/09/07/tci-toolbox-controls-installer.aspx#comments</comments><description>&lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;TCI is a VS Package that is provided by the VS SDK as a redist. TCI allows you to easily add&amp;nbsp;your custom&amp;nbsp;Control to the VS Toolbox. For a brief introduction to TCI you can check the VS SDK documentation. Here I will try to cover what is happening under cover:  &lt;/p&gt;&lt;p&gt;When you want to add your custom control to the VS toolbox using the TCI VS Package all you need is to tell TCI where the assembly containing the control is and&amp;nbsp;notify&amp;nbsp;to TCI this event incrementing a registry key.&amp;nbsp;Probably the easier way to achieve these requirements is using a WIX-based installer (as the SDK sample does).  &lt;/p&gt;&lt;p&gt;In order to tell TCI where your control is&amp;nbsp;you can&amp;nbsp;use the&amp;nbsp;the fully qualified type name if you are installing the control in the GAC as following:  &lt;/p&gt;&lt;p&gt;&amp;lt;Registry Root="HKLM" Key="Software\Microsoft\VisualStudio\9.0\ToolboxControlsInstaller\GacControl, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1631b3e7a8fbcce5, processorArchitecture=MSIL" Value="Litware Controls" Type="string" /&amp;gt;  &lt;/p&gt;&lt;p&gt;Or provide a location where the assembly containing the control&amp;nbsp;is using the CodeBase value:  &lt;/p&gt;&lt;p&gt;&amp;lt;Registry Root="HKLM" Key="Software\Microsoft\VisualStudio\9.0\ToolboxControlsInstaller\NonGacControl, Version=1.0.0.0, Culture=neutral, PublicKeyToken=1631b3e7a8fbcce5, processorArchitecture=MSIL" Value="Litware Controls" Type="string"&amp;gt;&lt;br&gt;&amp;lt;Registry Name="Codebase" Value="[#AssemblyContainingTheFile.dll]" Type="string" /&amp;gt;&lt;br&gt;&amp;lt;/Registry&amp;gt;  &lt;/p&gt;&lt;p&gt;Finally you have to include the MSM containing the custom actions which notify TCI that a new Control has been installed:  &lt;/p&gt;&lt;p&gt;&amp;lt;Merge Id="TbxCtrlsInstDefaultItemsCA" Language="1033" SourceFile="..\..\..\Redistributables\TbxCtrlsInstDefaultItemsCA.msm" DiskId="1" /&amp;gt;  &lt;/p&gt;&lt;p&gt;The custom action will increment or decrement the&amp;nbsp;"Default Items" value of the&amp;nbsp;following registry entry:  &lt;/p&gt;&lt;p&gt;[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\Packages\{2c298b35-07da-45f1-96a3-be55d91c8d7a}\Toolbox]&lt;br&gt;"Default Items"=dword:00000001  &lt;/p&gt;&lt;p&gt;Note that&amp;nbsp;the&amp;nbsp;{2c298b35-07da-45f1-96a3-be55d91c8d7a} is the GUID for the TCI VS Package.  &lt;/p&gt;&lt;p&gt;It's important to check if the TCI Redist is already installed before installing your custom controls if you targeting VS 2500. It's not necessary for VS codename "Orcas" because&amp;nbsp;TCI Package is already installed. You can find the TCI VS Package in the VS's Private Assemblies directory.&amp;nbsp;  &lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=3780964" width="1" height="1"&gt;</description><category domain="http://weblogs.asp.net/adalon/archive/tags/Orcas/default.aspx">Orcas</category><category domain="http://weblogs.asp.net/adalon/archive/tags/ASP.NET/default.aspx">ASP.NET</category><category domain="http://weblogs.asp.net/adalon/archive/tags/Visual+Studio/default.aspx">Visual Studio</category><category domain="http://weblogs.asp.net/adalon/archive/tags/.NET/default.aspx">.NET</category><category domain="http://weblogs.asp.net/adalon/archive/tags/WIX/default.aspx">WIX</category></item><item><title>GAX 1.3 is out!</title><link>http://weblogs.asp.net/adalon/archive/2007/08/05/gax-1-3-is-out.aspx</link><pubDate>Mon, 06 Aug 2007 01:01:00 GMT</pubDate><guid isPermaLink="false">c06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:3780530</guid><dc:creator>adalon</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://weblogs.asp.net/adalon/rsscomments.aspx?PostID=3780530</wfw:commentRss><comments>http://weblogs.asp.net/adalon/archive/2007/08/05/gax-1-3-is-out.aspx#comments</comments><description>&lt;p&gt;&lt;em&gt;&lt;font color="#808080"&gt;This post was originally published at &lt;/font&gt;&lt;/em&gt;&lt;a href="http://adrianalonso.blogspot.com"&gt;&lt;em&gt;&lt;font color="#808080"&gt;http://adrianalonso.blogspot.com&lt;/font&gt;&lt;/em&gt;&lt;/a&gt;&lt;/p&gt; &lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;This new version of GAX is a must if you are thinking to develop Guidance Packages&amp;nbsp;using&amp;nbsp;VS Codename "Orcas" (previous version of GAX didn't work&amp;nbsp;with the latest version of VS) and it will also provide some new features if your are developing with VS 2005.&lt;/p&gt; &lt;p&gt;A&amp;nbsp;welcomed “fix” is the&amp;nbsp;enhancement of the&amp;nbsp;registration process. Now it's&amp;nbsp;smarter&amp;nbsp;about&amp;nbsp;whether to install VB templates&amp;nbsp;based on the presence of VB as a Visual Studio's product.&amp;nbsp;This means that&amp;nbsp;if your Guidance Package contains VB templates (.vstemplates for VB projects or items) you won't need to&amp;nbsp;add conditional logic in your installer to avoid the registration failure when the package is being installed or registered.  &lt;p&gt;The GAX installer is also improved to use WIX technology but&amp;nbsp;the GAT installer project that is unfolded when you create a new Guidance Package using GAT is still the same VS Setup Project.  &lt;p&gt;At last, the Experimental Hive registration is now a built-in feature in GAX allowing you to register your Guidance Packages in both Normal and Experimental hives.  &lt;p&gt;So it seems that this CTP is a&amp;nbsp;necessary and welcomed&amp;nbsp;update&amp;nbsp;for the runtime but not for the UX of developing Guidance Packages.  &lt;p&gt;Here you have the links:  &lt;p&gt;- &lt;a href="http://blogs.msdn.com/agile/archive/2007/08/02/new-gax-gat-july-2007-released.aspx"&gt;Grigory Melnik's announcement&lt;/a&gt;&lt;br&gt;- &lt;a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=C0A394C0-5EEB-47C4-9F7B-71E51866A7ED&amp;amp;displaylang=en"&gt;GAX July 2007 CTP download&lt;/a&gt;&lt;br&gt;- &lt;a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=E3D101DB-6EE1-4EC5-884E-97B27E49EAAE&amp;amp;displaylang=en"&gt;GAT July 2007 CTP&amp;nbsp;download&lt;/a&gt;&lt;/p&gt;&lt;img src="http://weblogs.asp.net/aggbug.aspx?PostID=3780530" width="1" height="1"&gt;</description><category domain="http://weblogs.asp.net/adalon/archive/tags/Orcas/default.aspx">Orcas</category><category domain="http://weblogs.asp.net/adalon/archive/tags/Visual+Studio/default.aspx">Visual Studio</category><category domain="http://weblogs.asp.net/adalon/archive/tags/.NET/default.aspx">.NET</category><category domain="http://weblogs.asp.net/adalon/archive/tags/GAX/default.aspx">GAX</category><category domain="http://weblogs.asp.net/adalon/archive/tags/GAT/default.aspx">GAT</category><category domain="http://weblogs.asp.net/adalon/archive/tags/WIX/default.aspx">WIX</category></item></channel></rss>