Just testing clean install for now -----Original Message----- From: Chad Petersen [mailto:chad.peter...@harlandfs.com] Sent: Tuesday, May 10, 2011 2:27 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Publishing to GAC
I might have missed but does this happen during a clean install, upgrade or both? -----Original Message----- From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] Sent: Tuesday, May 10, 2011 1:05 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Publishing to GAC I remember reading about that. double checked, the entry in MsiAssemblyName has a version we are at a loss as to how to track down the problem. there are no errors. any ideas? -----Original Message----- From: Jacques Eloff [mailto:repst...@gmail.com] Sent: Tuesday, May 10, 2011 12:33 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Publishing to GAC Ahh, I found that when moving from WiX 2.0 to 3.0/3.5, the assembly file version wasn't written to the MsiAssemblyName table and it caused problems for us during upgrades. The solution in that case was just to add the -fv switch to Light, but that only solves upgrade issues. On Tue, May 10, 2011 at 8:41 AM, Kurt Jensen <kurt.jen...@us.ophiropt.com>wrote: > yes, we set the Assembly=".net" otherwise we would not get the log entry > listing our assembly. the assembly is properly listed in the MsiAssembly > table with attribute=0 > > we are converting a vs2008/wix3.0 project to vs2010/wix3.5. in the wix3.0 > project we only install it to the GAC. in the new wix3.5 we install it > both local and GAC. the source code for installing to the GAC is > identical in both projects. > > > <DirectoryRef Id="CONSOLESERVICEDIRECTORY"> > <Component Id="Spiricon.Interfaces.ConsoleService" Guid=""> > <File Source="$(var.Spiricon.Interfaces.ConsoleService.TargetPath)" > Assembly=".net" KeyPath="yes" /> > </Component> > </DirectoryRef> > > note that CONSOLESERVICEDIRECTORY is never actually created > > > > Make sure that the assembly is signed. > we are using strong naming but not code signing. same as in the wix3.0 > project. > > > surely we would see an entry in the log if there was a problem? > > > -----Original Message----- > From: Jacques Eloff [mailto:repst...@gmail.com] > Sent: Tuesday, May 10, 2011 9:01 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Publishing to GAC > > Did you set the Assembly attribute in the File element to ".net"? > > <File Assembly=".net" KeyPath="yes" Id="MyAssembly.dl" > Name="MyAssembly.dll" > ProcessorArchitecture="msil"/> > > Also, as I recall, you need to create a separate directory for the GAC'd > assembly. So you would have two <File> elements for the assembly with > different parent directories. One to actually install it to disk, the > other > one to install it into the GAC. > > Make sure that the assembly is signed. You can't install unsigned > assemblies > into the GAC. > > Take a look at Aaron's blog as well: > http://blogs.msdn.com/b/astebner/archive/2007/06/21/3450539.aspx > > Jacques > On Tue, May 10, 2011 at 7:46 AM, Kurt Jensen > <kurt.jen...@us.ophiropt.com>wrote: > > > we publish one assembly to the GAC. we find the MsiPublishAssemblies > > action > > in the log file. there is no error. > > > > but the assembly does not appear in the GAC. > > > > > > > > > > > > Action 7:17:10: MsiPublishAssemblies. Publishing assembly information > > > > MSI (s) (F8:2C) [07:17:10:015]: Executing op: > > > > > AssemblyPublish(Feature=ProductFeature,Component={F23AAD89-8D5F-46C1-879 2- > C7988BEF6212}[~]2,AssemblyType=1,,AssemblyName=Spiricon.Interfaces.Conso le > Service,version="1.0.0.0",culture="neutral",publicKeyToken="18293B57E84A EC > 4B",processorArchitecture="MSIL",) > > > > MsiPublishAssemblies: Application Context:Global, Assembly > > > > > Name:Spiricon.Interfaces.ConsoleService,version="1.0.0.0",culture="neutr al > ",publicKeyToken="18293B57E84AEC4B",processorArchitecture="MSIL" > > > > MSI (s) (F8:2C) [07:17:10:030]: Executing op: > > ActionStart(Name=PublishFeatures,Description=Publishing Product > > Features,Template=Feature: [1]) > > > > > > > > > > > > any ideas how to find out what is wrong? > > > > > > > > > > > > Kurt Jensen > > > > Senior Software Engineer > > > > Ophir-Spiricon LLC > > > > > > > > www.ophiropt.com/photonics <http://www.ophiropt.com/laser-measurement> > > > > > > > > > > > > The True Measure of Laser PerformanceT > > > > > ------------------------------------------------------------------------ -- > ---- > > Achieve unprecedented app performance and reliability > > What every C/C++ and Fortran developer should know. > > Learn how Intel has extended the reach of its next-generation tools > > to help boost performance applications - inlcuding clusters. > > http://p.sf.net/sfu/intel-dev2devmay > > _______________________________________________ > > WiX-users mailing list > > WiX-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------ -- > ---- > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > ------------------------------------------------------------------------ -- ---- > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------ -- ---- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------ ------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users -------------------------------------------------------------------------- ---- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users