Quote Originally Posted by PlausiblyDamp View Post
In that case I would normally take this on a case by case basis - e.g. if I only wanted to do one specific thing like change the title bar colour then I might just go ahead and do it via the API rather than include a large dependency. If on the other hand I could see a nuget package providing a lot of useful functionality then I would opt for nuget.

One big advantage of using nuget packages, or at least the quality ones, is that they are often well written and tested. They will deal with a lot of edge cases and odd behaviours which might not be obvious if you are implementing this behaviour yourself.
And if the Nuget package uses a technology that is not included in the standard Windows SDK, no standard APIs or interfaces, but offers you new possibilities through new APIs, etc., would you use this Nuget package or would you rather say, I won't use this Nuget package because Microsoft might abandon the technology used at some point?