search

wixtoolset / issues

WiX Toolset Issues Tracker
http://wixtoolset.org/
129 stars 36 forks source link

Heat doesn't harvest referenced assemblies #2639

Open wixbot opened 14 years ago

wixbot commented 14 years ago

Using heat to harvest a Visual Studio project with any of the options "-pog:Binaries -pog:Satellites -pog:Content" then the referenced assemblies are not included.

Just for clarification what I mean by referenced assemblies are non-framework assemblies referenced in the project that are copied to the bin folder, in my test case this would be log4net.dll but would also include interop files.

This makes the new harvest feature in WiX v3.5’s Votive very limited as most projects I work on have some sort of external assembly.

Originally opened by nsleigh from http://sourceforge.net/p/wix/bugs/2082/

wixbot commented 11 years ago

When you implement this please don't forget resource files of referenced assemblies. For example I have resources for two languages in a MVC web site. It correctly copied the resources for the main Web DLL into a DE (Germany) subdirectory (so the satellites Option works for that), but failed to copy the resources of the referenced assemblies.

wixbot commented 11 years ago

Harvesting references in Votive has been disabled by default for 3.5. Harvesting references should be added in 4.0.

wixbot commented 10 years ago

Originally changed by barnson Area changed from heat to ` Releasechanged fromfuturetov3.x`

wixbot commented 10 years ago

Originally changed by bmurri AssignedTo set to wixsupport

wixbot commented 10 years ago

Related: http://wixtoolset.org/issues/4379/

Originally posted by dandrejvv

letmaik commented 7 years ago

What's the status on this? Is this working in 4.x?

barnson commented 7 years ago

The bug is open and waiting for someone to claim it.

ragbnr commented 7 years ago

Any update on this bug? I am migrating from Wix 3.5 to 3.11 latest wix stable version. We do have reference assemblies harvest property set to true, so we do see build failure for those assemblies. Light.exe is throws below error. Meanwhile any workaround or solution will be appreciated.

error LGHT0231: The component 'cmp91D12B21312FEDB356BCFE322DCB4081.905FE1D5_1C5F_492A_B054_E9246FF088DC' has a key file with path 'TARGETDIR\travelport\smartpoint\0005.00.configurationserviceclient.dll'. Since this path is not rooted in one of the standard directories (like ProgramFilesFolder), this component does not fit the criteria for having an automatically generated guid. (This error may also occur if a path contains a likely standard directory such as nesting a directory with name "Common Files" under ProgramFilesFolder.)

robmen commented 7 years ago

The bug is still open and waiting for someone to claim it.

Maybe you can be that someone?

BMurri commented 7 years ago

Rob, I just noticed that I have an implementing patch lying around for this one.

ragbnr commented 7 years ago

@robmen : I would like to contribute but I am not an expert in Wix. But I would continue to learn and build expertise.

ragbnr commented 7 years ago

@BMurri : So do you have a workaround solution for error LGHT0231 w.r.t to harvested files?

robmen commented 7 years ago

@ragbnr See http://wixtoolset.org/development/

BMurri commented 7 years ago

I don't know if it would do anything about that error message, but it does allow you to select the various types of project output in order to capture satellites, dependencies, "content", etc. when harvesting.