Skip to content

Commit

Permalink
Make NuGetizer targets buildTransitive to fix SponsorLink
Browse files Browse the repository at this point in the history
For development-dependency packages, no assets flow across project
references, including build targets and package dependencies.
This is problematic for SponsorLink since it needs targets to properly
surface build properties to the analyzer that performs the checks.

By making NuGetizer build targets transitive, we fix the project to
project (P2P) scenario where one project installs NuGetizer and
referencing projects start failing the SponsorLink check because the
SL targets are missing. (since the package dependency on SL isn't
surfaced in that case).

By also including the SL targets in our package and conditionally
importing them if they haven't already been imported, we further
remove the changes that the missing dependency causes failures.

This might not be the optimal way to solve this, but it's the only
one that works consistently. This obviously causes P2P references
to a project consuming NuGetizer to *also* become nugetized
themselves. This should be a minor issue, however.
  • Loading branch information
kzu committed Mar 20, 2023
1 parent 0fab569 commit 85ede7a
Show file tree
Hide file tree
Showing 3 changed files with 15 additions and 5 deletions.
7 changes: 5 additions & 2 deletions src/CodeAnalysis/CodeAnalysis.csproj
Original file line number Diff line number Diff line change
Expand Up @@ -14,11 +14,14 @@
<PackageReference Include="ThisAssembly.AssemblyInfo" Version="1.1.3" PrivateAssets="all" />
<PackageReference Include="ThisAssembly.Strings" Version="1.1.3" PrivateAssets="all" />
<PackageReference Include="Microsoft.CodeAnalysis.CSharp" Version="4.0.1" Pack="false" />
<PackageReference Include="Devlooped.SponsorLink" Version="42.42.221-main" PrivateAssets="all" />
<PackageReference Include="Devlooped.SponsorLink" Version="0.10.0" GeneratePathProperty="true" />
</ItemGroup>

<ItemGroup>
<None Update="NuGetizer.CodeAnalysis.targets" PackFolder="build" CopyToOutputDirectory="PreserveNewest" />
<None Update="NuGetizer.CodeAnalysis.targets" PackFolder="buildTransitive" CopyToOutputDirectory="PreserveNewest" />
<None Include="$(PkgDevlooped_SponsorLink)\buildTransitive\Devlooped.SponsorLink.targets"
PackFolder="buildTransitive"
CopyToOutputDirectory="PreserveNewest" />
</ItemGroup>

</Project>
11 changes: 9 additions & 2 deletions src/CodeAnalysis/NuGetizer.CodeAnalysis.targets
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,6 @@

<CompilerVisibleProperty Include="Authors" />
<CompilerVisibleProperty Include="AssemblyName" />

<SponsorablePackageId Include="NuGetizer" />
</ItemGroup>

<Target Name="_AddDescription" BeforeTargets="GenerateMSBuildEditorConfigFileShouldRun">
Expand All @@ -29,4 +27,13 @@
</ItemGroup>
</Target>

<ItemGroup Label="SponsorLink">
<SponsorablePackageId Include="NuGetizer" />
</ItemGroup>

<!-- This ensures devlooped targets are imported transitively even if we are a dev dependency
and therefore don't propagate the SL dependency, which would otherwise cause a build error
due to analyzers being forcedly transitive even if the reference is private assets/dev dep.
-->
<Import Project="Devlooped.SponsorLink.targets" Condition="$(SponsorLinkImported) != true"/>
</Project>
2 changes: 1 addition & 1 deletion src/NuGetizer.Tasks/NuGetizer.Tasks.targets
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@
<Description>Simple, flexible and powerful NuGet packaging</Description>

<DevelopmentDependency>true</DevelopmentDependency>
<PackFolder>build</PackFolder>
<PackFolder>buildTransitive</PackFolder>

<PackOnBuild Condition="'$(PackOnBuild)' == '' And '$(Configuration)' == 'Release'">true</PackOnBuild>
<PackageOutputPath Condition="'$(PackageOutputPath)' == ''">..\..\bin</PackageOutputPath>
Expand Down

0 comments on commit 85ede7a

Please sign in to comment.