There is no indication of the failure to download NuGet.Build when it does fail.

[simonwgill]

My office firewall does not allow us to use the Microsoft forwarder link but using the http://packages.nuget.org/v1/FeedService.svc url as a source works normally. It would also fail if you were disconnected from nuget.org for some reason.

The reported error was not initially helpful. All it said was "Failed to add import 'NuGet.targets' to $project". Since this was a download error I would expect to see that as the reason.

Also, since the download will always fail in my situation, can you use the locally configured nuget sources to get NuGet.Build?

[davidfowl]

I can make it show the actual exception text as part of the error. You can change the powershell script to not hardcode the source and it'll just use the ones you have configured.

[simonwgill]

The exception text would help narrow down the issue in future. So that's great.

Changing the script without closing Visual Studio had no effect on the function. That's probably my lack of understanding on how all the scripts are loaded.

I don't understand why you hard-coded the source parameter in the first place though. What was the reason for that?

[davidfowl]

So I don't have to depend on your configured sources.