a clue! we are moving our vs2008 solution to vs2010. all of our vs2008 assemblies are stuck at the last release v5.5.4127.3070. all of our vs2010 assemblies are set to the default v1.0.0.0.
when I used the v5.5.4127.3070 assembly in the test (below) then it was installed in the GAC. if I rebuild the vs2010 as v1.1.0.0 then it is installed in the GAC apparently there is a bias against v1.0.0.0? -----Original Message----- From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] Sent: Wednesday, May 11, 2011 6:38 AM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Publishing to GAC ok, here it is trimmed down to its essence. I created a new project, enabled the default component, added a dummy file, then added my GAC component. on running the MSI, Spiricon.Interfaces.ConsoleService.dll is not in the GAC <?xml version="1.0" encoding="UTF-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi";> <Product Id="4dd987d3-2e96-4eeb-892a-bb016fe0905a" Name="SetupProject1" Language="1033" Version="1.0.0.0" Manufacturer="SetupProject1" UpgradeCode="a9f3d24a-59f8-47f6-8efe-969980b94136"> <Package InstallerVersion="200" Compressed="yes" /> <Media Id="1" Cabinet="media1.cab" EmbedCab="yes" /> <Directory Id="TARGETDIR" Name="SourceDir"> <Directory Id="ProgramFilesFolder"> <Directory Id="INSTALLLOCATION" Name="SetupProject1"> <!-- TODO: Remove the comments around this Component element and the ComponentRef below in order to add resources to this installer. --> <Component Id="ProductComponent" Guid="9e33d5df-e36a-4a40-844b-bda6688801b0"> <File Source="$(var.ProjectDir)OSIBanner.JPG" KeyPath="yes" /> <!-- TODO: Insert files, registry keys, and other resources here. --> </Component> <Component Id="Spiricon.Interfaces.ConsoleService" Guid="F23AAD89-8D5F-46c1-8792-C7988BEF6212"> <File Source="$(var.TargetDir)\Spiricon.Interfaces.ConsoleService.dll" Assembly=".net" KeyPath="yes" /> </Component> </Directory> </Directory> </Directory> <Feature Id="ProductFeature" Title="SetupProject1" Level="1"> <!-- TODO: Remove the comments around this ComponentRef element and the Component above in order to add resources to this installer. --> <ComponentRef Id="ProductComponent" /> <ComponentRef Id="Spiricon.Interfaces.ConsoleService" /> <!-- Note: The following ComponentGroupRef is required to pull in generated authoring from project references. --> <ComponentGroupRef Id="Product.Generated" /> </Feature> </Product> </Wix> -----Original Message----- From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] Sent: Wednesday, May 11, 2011 6:15 AM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Publishing to GAC sorry but did we run out of ideas? you say "There's not really a lot of info..." what info do you need? please ask. if I knew what info was pertinent then I might still be able to look for a solution. I searched bugs but could not find any related. I searched the web but could not find any related. searched and read extensively before posting the original question. been on this 3 days with no solution in sight. maybe someone remembers some issue or bug that relates but is titled differently. is there someone I can pay to help me solve this problem? I don't know where else to look. -----Original Message----- From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] Sent: Tuesday, May 10, 2011 3:25 PM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] Publishing to GAC yes, two components with different guids and different directories as outlined in the suggested article and follow on articles - I read them all I will look closer from some aberration in the log file. guid="" is just to make it more readable... there is a real guid in the actual code how do I copy and display "MsiAssembly table of the MSI file for the assembly"? here is what I see... Component_ = Spiricon.Interfaces.ConsoleService Feature_ = ProductgFeature File_Manifest = File_Application = Attribute = 0 Kurt -----Original Message----- From: Wilson, Phil [mailto:phil.wil...@invensys.com] Sent: Tuesday, May 10, 2011 3:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Publishing to GAC There's not really a lot of info, but there are few things to look for. There won't be an error in the MSI log if Windows thinks it's doing the right thing, so don't just look for "error". There might be entries about "diallowing installation of component ....." that are relevant. If you're installing the file locally and also to the GAC you have two components with different guids, and different directories correct? Why have you got guid="" in your component? I'm not quite sure of the full effect of this on assemblies, but this means that Windows Installer won't register the component, so it's not clear to me exactly what you'd see in the log for that. It would also make sense for you to assign guids to those components so that you can actually search the log and see what Windows has to say about them. Exactly what is the MsiAssembly table of the MSI file for the assembly? If it's going into the GAC there must be an entry for the assembly with a null File_Application column. Phil Wilson -----Original Message----- From: Kurt Jensen [mailto:kurt.jen...@us.ophiropt.com] Sent: Tuesday, May 10, 2011 1:31 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Publishing to GAC 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 *** Confidentiality Notice: This e-mail, including any associated or attached files, is intended solely for the individual or entity to which it is addressed. This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify the sender immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person. This email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please go to http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id= 77. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail recept...@invensys.com. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). -------------------------------------------------------------------------- ---- 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
