Ok, regfree won't work for you. By chance do any of the other binaries refer to your shell extension?
You should be able to unregister the one in the debug folder by using regasm. On Jul 27, 2013, at 12:45 PM, "Marco Tognacci" <mark...@live.it> wrote: > I need to register this dll for registering a shell extension to provide > custom preview for my custom file extension.My setup project is contained in > the my application project folder, but I compile it with a stand alone > solution, where I'm refer to the building folder of my Application, Release > or Debug depend on the building option of the setup.The dll could be register > in the system, as it is used for a shell extension and if I build it locally > I can't know if it's registered.I should unregister it before calling > heat.exe? If it's registered in the system Heat could refer to this previous > registered dll instead of that there is on the location that is taken as > source for the setup? > >> From: jacob.hoo...@greenheck.com >> To: wix-users@lists.sourceforge.net >> Date: Sat, 27 Jul 2013 17:26:06 +0000 >> Subject: Re: [WiX-users] HeatFile not works if build in Release >> >> Is your DLL project output set to register for COM interop? Are you building >> your install as part of the solution containing the source projects? Have >> you ensured your assembly is not registered prior to building the installer >> project? >> >> Have you tried to manually run heat against the release folder to see if it >> works out of process? (When building, I believe the heat task will emit the >> command line params to the MSBuild output window.) >> >>> From what I remember, Heat is using registry redirection to capture the >>> changes, so the heat task won't actually register the assembly locally as >>> it kills the redirected keys after converting them to Wix output. >> >> Finally, do you intend on sharing this assembly among multiple applications? >> If not, you might want to look into registration free COM and ignore the >> registry all together. >> >> -----Original Message----- >> From: Marco Tognacci [mailto:mark...@live.it] >> Sent: Saturday, July 27, 2013 7:46 AM >> To: General discussion for Windows Installer XML toolset. >> Subject: Re: [WiX-users] HeatFile not works if build in Release >> >> I have build it first on Debug mode and then on Release. Could be that the >> first time Hear register the dll in the Debug folder and then the second >> time instead of register the dll in the Release folder it it return the path >> of the dll in the debug folder because in the systerm is register the on in >> the debug folder?In this case is there a way for registering each time the >> new dll using HeatFile or I have to add some command line for deregistering >> the dll myself? >> >>> From: mark...@live.it >>> To: wix-users@lists.sourceforge.net >>> Date: Fri, 26 Jul 2013 23:49:31 +0200 >>> Subject: Re: [WiX-users] HeatFile not works if build in Release >>> >>> I have checked it, registering it using a custom exe and using c# >>> RegistrationServices.RegisterAssembly, the line added to the registry are >>> equal to that harvested by Heat.I can't make it hard coded as I would >>> change the version and even if my dll will expose other interfaces.Using >>> Heat I need to make 2 msi project for registering under x86 and x64 depends >>> on OS of the machine where to install, so I need to change the path of the >>> dll in the x64 project as it has to link the same x86 dll. >>> >>> >>>> Date: Fri, 26 Jul 2013 14:21:59 -0700 >>>> From: os...@live.com >>>> To: wix-users@lists.sourceforge.net >>>> Subject: Re: [WiX-users] HeatFile not works if build in Release >>>> >>>> I'm not recommending running an exe during installation. Instead I'm >>>> suggesting taking that DLL you are passing to the heat tool and >>>> registering it into a VM to double check what it is writing. >>>> >>>> >>>> Marco Tognacci <mark...@live.it> wrote: >>>> >>>> I prefer not to run exe files for registring dll during installation, I'd >>>> like to add only the registry keys that I need, and make it with the >>>> msi.As I have made in debug works but I can't figure out why in Release >>>> don't work.Perhaps a bug in the Heat.exe ??? >>>> >>>>> Date: Fri, 26 Jul 2013 14:03:12 -0700 >>>>> From: os...@live.com >>>>> To: wix-users@lists.sourceforge.net >>>>> Subject: Re: [WiX-users] HeatFile not works if build in Release >>>>> >>>>> I also suggest you do a regsvr32 on your release DLL and ensure that the >>>>> codebase value in the registry is correct. >>>>> >>>>> Also check your build spew to double check the command line passed to the >>>>> heat utility. >>>>> >>>>> >>>>> John Cooper <jocoo...@jackhenry.com> wrote: >>>>> >>>>> I would expect DirectoryRefId to match the Directory@Id you're >>>>> substituting. However, this should cause it to break in both >>>>> Configurations, so I suspect that's not it. >>>>> >>>>> Is this Release configuration build breaking on a build server, both >>>>> locally and on a build server, or just locally? I note you're >>>>> redirecting the output from the default, and that can cause serious >>>>> breakage and performance problems on a TFS build server. >>>>> >>>>> -- >>>>> John Merryweather Cooper >>>>> Build & Install Engineer - ESA >>>>> Jack Henry & Associates, Inc.(r) >>>>> Shawnee Mission, KS 66227 >>>>> Office: 913-341-3434 x791011 >>>>> jocoo...@jackhenry.com >>>>> www.jackhenry.com >>>>> >>>>> >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: Marco Tognacci [mailto:mark...@live.it] >>>>> Sent: Friday, July 26, 2013 2:49 PM >>>>> To: General discussion for Windows Installer XML toolset. >>>>> Subject: Re: [WiX-users] HeatFile not works if build in Release >>>>> >>>>> I have added a node in the setup project in the Before build sections >>>>> <Target Name="BeforeBuild"> >>>>> <HeatFile File="..\distribution\Bin\$(Configuration)" >>>>> PreprocessorVariable="var.HarvestPath" >>>>> OutputFile="HeatGeneratedFile.wxs" >>>>> ComponentGroupName="HeatGenerated" >>>>> DirectoryRefId="INSTALLFOLDER" >>>>> AutogenerateGuids="true" >>>>> ToolPath="$(WixToolPath)" >>>>> SuppressFragments="true" >>>>> SuppressRegistry="false" SuppressCom="false" >>>>> SuppressUniqueIds="true" >>>>> SuppressRootDirectory="true" >>>>> Transforms="MyTransform.xslt"/> </Target> in MyTransform.xslt I have >>>>> added the code to change the string "file:///[#myFile.dll]" with >>>>> "[INSTALLATIONFOLDER]myFile.dll"It all works fine if I compile in Debug >>>>> mode, but in Release I can't make it works as I have the specific full >>>>> path that depends on the location of the file and it's not relative. >>>>> >>>>> >>>>>> Date: Fri, 26 Jul 2013 11:49:10 -0700 >>>>>> From: os...@live.com >>>>>> To: wix-users@lists.sourceforge.net >>>>>> Subject: Re: [WiX-users] HeatFile not works if build in Release >>>>>> >>>>>> How are you calling HeatFile? >>>>>> >>>>>> >>>>>> Marco Tognacci <mark...@live.it> wrote: >>>>>> >>>>>> I have used HeatFile in my setup project to harvest a dll for register >>>>>> it for COMIf I build my project in Debug mode I have this: >>>>>> <Component Id="cmpA8B0842041500B0ACE61F7EFD0FBD893" >>>>>> Directory="dir0F6F75DF46D1BACE2233EC573E6D4AA9" Guid="PUT-GUID-HERE"> >>>>>> <File Id="myFile.dll" KeyPath="yes" >>>>>> Source="$(var.SourcePath)\myFile.dll" /> >>>>>> >>>>>> <RegistryValue Root="HKCR" >>>>>> Key="CLSID\{0A89A860-D7B1-11CE-8350-444553540000}\InprocServer32" >>>>>> Name="CodeBase" Value="file:///[#myFile.dll]" Type="string" >>>>>> Action="write" /> >>>>>> ... >>>>>> </Component> >>>>>> >>>>>> But if I build the project in Release mode I have this: >>>>>> <Component Id="cmpA8B0842041500B0ACE61F7EFD0FBD893" >>>>>> Directory="dir0F6F75DF46D1BACE2233EC573E6D4AA9" Guid="PUT-GUID-HERE"> >>>>>> <File Id="myFile.dll" KeyPath="yes" >>>>>> Source="$(var.SourcePath)\myFile.dll" /> >>>>>> >>>>>> <RegistryValue Root="HKCR" >>>>>> Key="CLSID\{0A89A860-D7B1-11CE-8350-444553540000}\InprocServer32" >>>>>> Name="CodeBase" Value="C:\MyProgramfolder\Bin\Debug\myFile.dll" >>>>>> Type="string" Action="write" /> >>>>>> ... >>>>>> </Component> >>>>>> >>>>>> I have in the RegistryValue @Value attribute the full path of the >>>>>> myFile.dll in the debug folder of my application.I have checked the >>>>>> project and all the points where could appear Debug or Release I have >>>>>> set $(Configuration), even the variable SourcePath is located using >>>>>> $(Configuration).Is it a bug in Heat? or I'm missing something? >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ---------------------------------------------------------------- >>>>>> ------ >>>>>> -------- See everything from the browser to the database with >>>>>> AppDynamics Get end-to-end visibility with application >>>>>> monitoring from AppDynamics Isolate bottlenecks and diagnose root cause >>>>>> in seconds. >>>>>> Start your free trial of AppDynamics Pro today! >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ >>>>>> ostg.c lktrk _______________________________________________ >>>>>> WiX-users mailing list >>>>>> WiX-users@lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>>>> >>>>>> ---------------------------------------------------------------- >>>>>> ------ >>>>>> -------- See everything from the browser to the database with >>>>>> AppDynamics Get end-to-end visibility with application >>>>>> monitoring from AppDynamics Isolate bottlenecks and diagnose root cause >>>>>> in seconds. >>>>>> Start your free trial of AppDynamics Pro today! >>>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ >>>>>> ostg.c lktrk _______________________________________________ >>>>>> WiX-users mailing list >>>>>> WiX-users@lists.sourceforge.net >>>>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>>> >>>>> ------------------------------------------------------------------ >>>>> ------------ See everything from the browser to the database with >>>>> AppDynamics Get end-to-end visibility with application monitoring from >>>>> AppDynamics Isolate bottlenecks and diagnose root cause in seconds. >>>>> Start your free trial of AppDynamics Pro today! >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/os >>>>> tg.clktrk _______________________________________________ >>>>> WiX-users mailing list >>>>> WiX-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>>> NOTICE: This electronic mail message and any files transmitted >>>>> with it are intended exclusively for the individual or entity to >>>>> which it is addressed. The message, together with any attachment, may >>>>> contain confidential and/or privileged information. >>>>> Any unauthorized review, use, printing, saving, copying, >>>>> disclosure or distribution is strictly prohibited. If you have >>>>> received this message in error, please immediately advise the sender by >>>>> reply email and delete all copies. >>>>> >>>>> >>>>> ------------------------------------------------------------------ >>>>> ------------ See everything from the browser to the database with >>>>> AppDynamics Get end-to-end visibility with application monitoring >>>>> from AppDynamics Isolate bottlenecks and diagnose root cause in >>>>> seconds. >>>>> Start your free trial of AppDynamics Pro today! >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/os >>>>> tg.clktrk _______________________________________________ >>>>> WiX-users mailing list >>>>> WiX-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>>> >>>>> ------------------------------------------------------------------ >>>>> ------------ See everything from the browser to the database with >>>>> AppDynamics Get end-to-end visibility with application monitoring >>>>> from AppDynamics Isolate bottlenecks and diagnose root cause in >>>>> seconds. >>>>> Start your free trial of AppDynamics Pro today! >>>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/os >>>>> tg.clktrk _______________________________________________ >>>>> WiX-users mailing list >>>>> WiX-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>> >>>> -------------------------------------------------------------------- >>>> ---------- See everything from the browser to the database with >>>> AppDynamics Get end-to-end visibility with application monitoring >>>> from AppDynamics Isolate bottlenecks and diagnose root cause in >>>> seconds. >>>> Start your free trial of AppDynamics Pro today! >>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg >>>> .clktrk _______________________________________________ >>>> WiX-users mailing list >>>> WiX-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>>> >>>> -------------------------------------------------------------------- >>>> ---------- See everything from the browser to the database with >>>> AppDynamics Get end-to-end visibility with application monitoring >>>> from AppDynamics Isolate bottlenecks and diagnose root cause in >>>> seconds. >>>> Start your free trial of AppDynamics Pro today! >>>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg >>>> .clktrk _______________________________________________ >>>> WiX-users mailing list >>>> WiX-users@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> ---------------------------------------------------------------------- >>> -------- See everything from the browser to the database with >>> AppDynamics Get end-to-end visibility with application monitoring from >>> AppDynamics Isolate bottlenecks and diagnose root cause in seconds. >>> Start your free trial of AppDynamics Pro today! >>> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.c >>> lktrk _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics Get >> end-to-end visibility with application monitoring from AppDynamics Isolate >> bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users >> >> ------------------------------------------------------------------------------ >> See everything from the browser to the database with AppDynamics >> Get end-to-end visibility with application monitoring from AppDynamics >> Isolate bottlenecks and diagnose root cause in seconds. >> Start your free trial of AppDynamics Pro today! >> http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk >> _______________________________________________ >> WiX-users mailing list >> WiX-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wix-users > > ------------------------------------------------------------------------------ > See everything from the browser to the database with AppDynamics > Get end-to-end visibility with application monitoring from AppDynamics > Isolate bottlenecks and diagnose root cause in seconds. > Start your free trial of AppDynamics Pro today! > http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
