You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if HEAT would allow the creation of a fragment that contains a list of dependent DLLs when harvesting with the 'project' type (CSPROJ). This harvesting should allow for metadata filtering so you can do things like only harvesting DLLs that have CopyLocal=true or if the HintPath matches a certain regular expression (like only harvest NuGet included references). Currently, Heat is hard coded to append 'Output' to the name of the Common.targets and this is not how Referenced DLLs are output. HEAT would need to allow for a more flexible harvesting setup that can handle different naming conventions for MSBuil Common.targets
Originally opened by blamoureux
The text was updated successfully, but these errors were encountered:
It would be great if HEAT would allow the creation of a fragment that contains a list of dependent DLLs when harvesting with the 'project' type (CSPROJ). This harvesting should allow for metadata filtering so you can do things like only harvesting DLLs that have CopyLocal=true or if the HintPath matches a certain regular expression (like only harvest NuGet included references). Currently, Heat is hard coded to append 'Output' to the name of the Common.targets and this is not how Referenced DLLs are output. HEAT would need to allow for a more flexible harvesting setup that can handle different naming conventions for MSBuil Common.targets
The text was updated successfully, but these errors were encountered: