cheers rob, got it sorted in the end FYI this is my custom protocol handler:
<RegistryKey Id="regCaseFlowKey" Action="createAndRemoveOnUninstall" Key="nameofmyprotocol" Root="HKCR"> <RegistryValue Id="DefaultValue" Action="write" Value="URL:my custom protocoll" Type="string" /> <RegistryValue Id="uriProtocol" Action="write" Name="URL Protocol" Value="" Type="string" /> <RegistryKey Id="DefaultIcon" Action="createAndRemoveOnUninstall" Key="DefaultIcon" > <RegistryValue Id="DefaultIconValue" Action="write" Value="myLauncher.exe" Type="string" /> </RegistryKey> <RegistryKey Id="regShell" Action="createAndRemoveOnUninstall" Key="shell" > <RegistryKey Id="regShellOpen" Action="createAndRemoveOnUninstall" Key="open" > <RegistryKey Id="regShellOpenCommand" Action="createAndRemoveOnUninstall" Key="command"> <RegistryValue Id="DefaultPathValue" Action="write" Value='"[INSTALLLOCATION]myLauncher.exe" "%1"' Type="string" /> </RegistryKey> </RegistryKey> </RegistryKey> </RegistryKey> Rob Mensching-2 wrote: > > RegistryKey is the parent of RegistryValue. Or you can just list a bunch > of RegistryValue elements out flat. Both ways work. > > -----Original Message----- > From: Barry Larkin [mailto:barrylar...@gmail.com] > Sent: Tuesday, January 20, 2009 03:33 > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] installing Outlook Primary Interop Assemblies > > hi guys, > thanks for that, we will look into the setupbld options for bootstrapping > > yes the protocol handler is just registry keys, i couldnt find a clean > example of creating registry keys within registry keys int the tutorial. > > cheers, > barry > > > Re: [WiX-users] installing Outlook Primary Interop Assemblies > From: Rob Mensching <rob.mensch...@mi...> - 2009-01-15 15:57 > 1. That's exactly what setupbld was designed for. It doesn't support many > more scenarios than that today. In WiX v3.5 burn will be much more > powerful. > > 2. Isn't a protocol handler just a set of registry keys? You just use the > RegistryKey/RegistryValue elements to write the keys based on MSDN, right? > > -----Original Message----- > From: Rainer Stropek [mailto:rai...@so...] > Sent: Wednesday, January 14, 2009 23:32 > To: 'General discussion for Windows Installer XML toolset.' > Subject: Re: [WiX-users] installing Outlook Primary Interop Assemblies > > Hi Barry! > > I had a similar problem with the Outlook PIA (in my case version 2007). I > solved it by building a bootstrapper that firstly installs the PIA and > then > our application. It works fine! Here is how you can do it: > > 1. Get the Office PIA Redistributable > > (http://www.microsoft.com/downloads/details.aspx?familyid=59DAEBAA-BED4-4282 > -A28C-B864D8BFA513&displaylang=en) > 2. Extract the o2007PIA.msi file > 3. Create the msi file for you app > 4. Create the bootstrapper (e.g. in a post-build event): > "c:\Program Files (x86)\Windows Installer XML v3\bin\setupbld.exe" > -out "$(TargetDir)MyInstaller.exe" > -mcs "$(ProjectDir)Chained_Msi\o2007pia.msi" > -mcs "$(TargetPath)" > -setup "c:\Program Files (x86)\Windows Installer XML v3\bin\setup.exe" > -title MyApp > > If Office PIA is not available on the computer on which you install the > resulting exe, it will be installed. If it is already there the Office > Redist will note that and do nothing. > > Unfortunately I cannot help with the custom protocol handler, sorry. > > Hope this helps. > > Kind regards, > Rainer. > > > On Wed, Jan 14, 2009 at 4:37 PM, Barry Larkin <barrylar...@gmail.com> > wrote: > >> Hi There, >> I am looking into using WIX instead of the standard windows setup and >> deployment project for the deployment of a solution to one of our >> clients >> in work. >> (The appication interacts with outlook using the outlook interop >> assemblies >> and is written in c# VS.NET 2005). >> >> I have read through the tutorial and I have installed WIX 3. >> >> the application i want to install will need to >> 1. check for the .net framework and install if version not present. >> 2. check for office 2003/xp PIA assemblies and install of not present >> 3. add a custom protol handler to the registry >> >> Can anyone point me in the right direction for information on creating >> some >> kind of bootstrap installer for .net and the PIA asssemblies. >> >> Also i am having some difficulties with creating nested registry entries. >> i >> cannot seem to get the correct syntax for creating registry keys within >> registry keys >> >> my application needs to define a custom protocol handler in the registry: >> http://msdn.microsoft.com/en-us/library/aa767914(VS.85).aspx<http://msdn.microsoft.com/en-us/library/aa767914%28VS.85%29.aspx> >> if anyone could show me how to create these registry enties using wix i >> would be very grateful! >> >> Kind regards, >> Barry >> >> >> >> >> >> > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > SourcForge Community > SourceForge wants to tell your story. > http://p.sf.net/sfu/sf-spreadtheword > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > -- View this message in context: http://n2.nabble.com/installing-Outlook-Primary-Interop-Assemblies-tp2157791p2237929.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users