i would linke to create a nuget package that allows me to add a file.cs during both install and restore phase of nuget package.
This file must be have as build action “C# Compiler”.
I’ve tryed different approach, but nothing succeded. I managed to copy file to the root of target project (as a link) but its build action is just “content”

Is there a consensus regarding which framework(s) a C# library should target when the goal is to publish it on NuGet and the author wants to reach developers who use “reasonably” up-to-date frameworks? In other words it’s safe to exclude outdated frameworks like net45, netstandard1.x, etc.

It is my first time creating and hosting a Nuget package (company’s Nuget , not public nuget-) so I just want some overall guideline approach:

I have two C# libraries A and B that usually are developed and versioned independently. Both have their own Git repos and each is published to a central Nuget repository. B depends on A.