Heat (in a "default" state) runs the DLLs passed to it in a self-reg-in-a-sandbox environment, so yes, that dll is modifying those registry values.
-----Original Message----- From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] Sent: Tuesday, July 21, 2009 2:38 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] TCP/IP Corruption After Uninstallation of WiX-generated MSI Right now I am using -sreg -scom -svb6 on that particular invocation of heat. There are other files included in that execution so I'm hoping that nothing really needs any of that registration stuff. But, if I am understanding you correctly, that dll really is modifying those registry keys/values during a self-reg process!? Edwin G. Castro Software Developer - Staff Electronic Banking Services Fiserv Office: 503-746-0643 Fax: 503-617-0291 www.fiserv.com Please consider the environment before printing this e-mail > -----Original Message----- > From: Neil Sleightholm [mailto:n...@x2systems.com] > Sent: Tuesday, July 21, 2009 12:02 PM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] TCP/IP Corruption After Uninstallation of WiX- > generated MSI > > Edwin > > I don't have those on my machine but I would guess that it does some > anti-social stuff when you self register it. Is there any documentation > on how you are supposed to distribute it. You could try running heat > and ignoring the self-reg stuff. > > Neil > > -----Original Message----- > From: Christopher Painter [mailto:chr...@deploymentengineering.com] > Sent: 21 July 2009 17:42 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] TCP/IP Corruption After Uninstallation of WiX- > generated MSI > > > Actually, it's redistributable: > > http://blogs.msdn.com/gertd/archive/2008/08/22/redist.aspx > > %ProgramFiles%\Microsoft Visual Studio 9.0\VSTSDB\redist-enu.txt > Subject to the license terms for the software, you may redistribute the > files (unmodified) listed below. > DatabaseSchemaProviders.Extensions.xml > Microsoft.Data.Schema.dll > Microsoft.Data.Schema.ScriptDom.dll > Microsoft.Data.Schema.ScriptDom.Sql.dll > Microsoft.Data.Schema.Sql.dll > Microsoft.Data.Schema.resources.dll > Microsoft.Data.Schema.ScriptDom.resources.dll > Microsoft.Data.Schema.ScriptDom.Sql.resources.dll > Microsoft.Data.Schema.Sql.resources.dll > vsdbcmd.exe > > > --- On Tue, 7/21/09, Neil Sleightholm <n...@x2systems.com> wrote: > > > From: Neil Sleightholm <n...@x2systems.com> > > Subject: Re: [WiX-users] TCP/IP Corruption After Uninstallation of > WiX-generated MSI > > To: "General discussion for Windows Installer XML toolset." <wix- > us...@lists.sourceforge.net> > > Date: Tuesday, July 21, 2009, 9:09 AM > > Just a thought but why are you > > distributing Microsoft.Data.Schema.Sql.dll that sounds like > > a Microsoft component to me and should be distributed using > > their package (presumably SQL). > > > > Neil > > > > -----Original Message----- > > From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com] > > > > Sent: 21 July 2009 00:05 > > To: General discussion for Windows Installer XML toolset. > > Subject: [WiX-users] TCP/IP Corruption After Uninstallation > > of WiX-generated MSI > > > > Today I found myself googling for a way to fix TCP/IP on my > > dev machine after uninstall corrupted TCP/IP. I remembered, > > after about 1.5 hours, that somebody had a similar problem > > about a month ago. In his case, he was converting an > > InstallShield package to WiX. I’m writing my package from > > scratch. *We are both using heat.exe.* > > > > After reading Chris Painters post at > http://blog.deploymentengineering.com/2007/08/hotfix-com-extraction- > causes-system.html > > I looked through the Registry table of my package to see if > > I could find the keys described in the InstallShield hotfix > > but didn't find any of them. I did find the following: > > > > Root: 2 > > Key: System\CurrentControlSet\Services\WinSock2\Parameters > > Name: WinSock_Registry_Version > > Value: 2.0 > > > > Root: 2 > > Key: > > > System\CurrentControlSet\Services\WinSock2\Parameters\NameSpace_Catalog > 5 > > Name: Num_Catalog_Entries > > Value: #0 > > > > Root: 2 > > Key: > > > System\CurrentControlSet\Services\WinSock2\Parameters\NameSpace_Catalog > 5 > > Name: Serial_Access_Num > > Value: #1 > > > > Root: 2 > > Key: > > > System\CurrentControlSet\Services\WinSock2\Parameters\NameSpace_Catalog > 5\Catalog_Entries > > Name: <null> > > Value: <null> > > > > Root: 2 > > Key: > > > System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9 > > Name: Num_CatalogEntries > > Value: #0 > > > > Root: 2 > > Key: > > > System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9 > > Name: Next_Catalog_Entry_ID > > Value: #1001 > > > > Root: 2 > > Key: > > > System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Catalog9 > > Name: Serial_Access_Num > > Value: #1 > > > > All of these rows were associated with the same component > > which was associated with *Microsoft.Data.Schema.Sql.dll.* > > > > I looked at the generated source and found: > > > > <Component Id="cmp..." Directory="dir..." Guid="*"> > > <File Id="fil..." KeyPath="yes" > > Source="SourceDir\Database\Microsoft.Data.Schema.Sql.dll" > > /> > > <RegistryValue Root="HKLM" > > Key="Software\Microsoft\Tracing\RASAPI32" > > Name="EnableFileTracing" Value="0" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > Key="Software\Microsoft\Tracing\RASAPI32" > > Name="EnableConsoleTracing" Value="0" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > Key="Software\Microsoft\Tracing\RASAPI32" > > Name="FileTracingMask" Value="-65536" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > Key="Software\Microsoft\Tracing\RASAPI32" > > Name="ConsoleTracingMask" Value="-65536" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > Key="Software\Microsoft\Tracing\RASAPI32" Name="MaxFileSize" > > Value="1048576" Type="integer" Action="write" /> > > <RegistryValue Root="HKLM" > > Key="Software\Microsoft\Tracing\RASAPI32" > > Name="FileDirectory" Value="C:\WINDOWS\tracing" > > Type="string" Action="write" /> > > <RegistryValue Root="HKLM" > > Key="Software\Microsoft\Tracing" Name="EnableConsoleTracing" > > Value="0" Type="integer" Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Control\MediaProperties\PrivateProperties > \Joystick\Winmm" > > Name="wheel" Value="1" Type="integer" Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Services\WinSock2\Parameters\NameSpace_Ca > talog5\Catalog_Entries" > > Value="" Type="string" Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Services\WinSock2\Parameters\NameSpace_Ca > talog5" > > Name="Num_Catalog_Entries" Value="0" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Services\WinSock2\Parameters\NameSpace_Ca > talog5" > > Name="Serial_Access_Num" Value="1" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Cat > alog9\Catalog_Entries" > > Value="" Type="string" Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Cat > alog9" > > Name="Num_Catalog_Entries" Value="0" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Cat > alog9" > > Name="Next_Catalog_Entry_ID" Value="1001" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > > Key="System\CurrentControlSet\Services\WinSock2\Parameters\Protocol_Cat > alog9" > > Name="Serial_Access_Num" Value="1" Type="integer" > > Action="write" /> > > <RegistryValue Root="HKLM" > > Key="System\CurrentControlSet\Services\WinSock2\Parameters" > > Name="WinSock_Registry_Version" Value="2.0" Type="string" > > Action="write" /> > > </Component> > > > > My first gut impression is _craziness!_ This must have just > > been random coincidence, right? I see "Joystick" in there... > > Microsoft.Data.Schema.Sql.dll can't possibly care about the > > joystick, could it? > > > > Anyway, this smells like a bug to me but I don't know > > enough to determine if this is really a heat.exe bug. I can > > filter out these entries easily enough so I have a > > workaround for now. Is this really a bug? > > > > > > Edwin G. Castro > > Software Developer - Staff > > Electronic Banking Services > > Fiserv > > Office: 503-746-0643 > > Fax: 503-617-0291 > > www.fiserv.com > > Please consider the environment before printing this > > e-mail > > > > --------------------------------------------------------------------- > --------- > > Enter the BlackBerry Developer Challenge > > This is your chance to win up to $100,000 in prizes! For a > > limited time, > > vendors submitting new applications to BlackBerry App > > World(TM) will have > > the opportunity to enter the BlackBerry Developer > > Challenge. See full prize > > details at: http://p.sf.net/sfu/Challenge > > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > --------------------------------------------------------------------- > --------- > > Enter the BlackBerry Developer Challenge > > This is your chance to win up to $100,000 in prizes! For a > > limited time, > > vendors submitting new applications to BlackBerry App > > World(TM) will have > > the opportunity to enter the BlackBerry Developer > > Challenge. See full prize > > details at: http://p.sf.net/sfu/Challenge > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > > > ----------------------------------------------------------------------- > ------- > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ----------------------------------------------------------------------- > ------- > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
