I actually think that we should revisit NuGet. When we last tried it, we didn't have any definitive scenario for it that wouldn't be covered by any other system. Now we have one. MSBuild tasks and such (which requires target injection into the project) is NuGet-specific, and, on the other hand, applicable to any MSBuild project. I think that is a valid case to argue now.
If we can do that, then there's less hassle overall, because there's no need to maintain two different methods, or fork and maintain (and regularly pull) code etc.
If we can do that, then there's less hassle overall, because there's no need to maintain two different methods, or fork and maintain (and regularly pull) code etc.