> 2. Download the library using a web browser, and just put it where it needs to be.
That might work for certain projects, but let's say you're using 10 third-party libraries. If they're under active development, you can expect at least a few security updates between the time you first import them and the time you ship your own product.
It's not very practical (especially for a programmer!) to keep manually checking your dependencies' product pages for updates.
1. Nuget packages inside Visual Studio 2. Download the library using a web browser, and just put it where it needs to be.
I'm sure some people would scoff at this list, but it does demonstrate that you can certainly use third party libraries without using git.