Based on this question: Prevent duplicating files in NuGet content and contentFiles folders, I'm using build/Project.targets
file of my NuGet package to add some files to project build output. Like:
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup>
<Content Include="$(MSBuildThisFileDirectory)..\tools\test.jpg">
<Link>test.jpg</Link>
<Visible>false</Visible>
<CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
<CopyToPublishDirectory>PreserveNewest</CopyToPublishDirectory>
</Content>
</ItemGroup>
</Project>
Now, I actually want those files to be visible in Solution Explorer, so that developer can tweak item properties. But setting the <Visible>
tag to true
makes no effect. Is this even possible?
I'd be happy even with a completely different approach that still allows the NuGet package to add files to project build output for both packages.config
and PackageReference
formats, yet show the files in Solution Explorer.
The global-packages folder is where NuGet installs any downloaded package. Each package is fully expanded into a subfolder that matches the package identifier and version number. Projects using the PackageReference format always use packages directly from this folder.
To open this file in the explorer, right-click on it. And choose open with, and then select NuGet Package Explorer.
NET or . NET Core project. After you install a NuGet package, you can then make a reference to it in your code with the using <namespace> statement, where <namespace> is the name of package you're using. After you've made a reference, you can then call the package through its API.
Showing NuGet package item added using .targets file in Solution Explorer
I am afraid you could not do such things by using .targets
file. That because when you add item by using .target
file, this item was added to your project like "Add As Link". That means this item hasn't really been added to your project. So it is not show in Solution Explorer.
To resolve this issue, you can create two nuget packages, using nuget content
for packages.config
formats and contentFiles
for PackageReference
formats.
Hope this helps.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With