Would love to see a VSIX feed (didn't see a way to vote for this feature).

Yes, most definitely. See KB#1072 - ProGet vs. NuGet.Server

Can you try pointing the extension at the 32-bit MSBuild (or 64-bit if you are already using the 32-bit version)? Beyond that, have you seen: http://blog.nikosbaxevanis.com/2013/10/04/how-to-configure-msbuild-to-locate-the-fsharp-build-targets/

Most definitely not. Unfortunately, we have no idea when NuGet v3 will come out, nor do we know when/if there will be API docs availalble (or a stable codebase to reverse engineer the API). Based on the various iterations of the v3 API that have been published in preview/beta, we have little confidence that it will solve the performace problems that ProGet users experience with connected/remote packages; so, on the ProGet Roadmap, we plan on solving that by creating a full index of nuget.org. That said, the NuGet team will need to support v2 for several years to come, so we're in no rush. Moreover, We have a plan that http://inedo.com/support/questions/3130

Regarding the first error – that sort of thing should only happen if the connector returns invalid data. What is the URL of the bower connector? For the registration, it looks like it’s just an HTTP 401. See this article for info about Bower & authentication in ProGet: http://inedo.com/support/kb/1095/introducing-bower-support-for-proget

You can pull the artifact out of _PublishedWebsites, or try the "This is a Web Application" checkbox. There is a transform config file action available as well, though you can store your configuration files in buildmaster.