From Commands, drag in the correct Tools | External Tool button. Next, right click in the Tookbar area and create a new Toolbar called NuGet. Launch Visual Studio 2008 and go to Tools | External Tools.Ĭommand (I’m assuming this is in the PATH): nuget.exeĪrguments: install -excludeversion -outputDirectory.
Maybe write a shim to get DTE automation working…īut that’s coulds and maybes. Use PowerShell scripts and batch files to get the most basic stuff working (get a package and update references.)
NET 2.0, 3.0, 3.5, and 4, but not everyone can upgrade.īackport the existing NuGet Package References dialog to 2008 using that version’s native extensions (not VSiX)Ĭreate MEF (Managed Extensibility Framework) plugins for the nuget.exe command-line to update the references in a vbproj or csproj Of course, the easiest thing is to just use 2010 as it sill supports. It’ll be interesting to see if there are folks in the community who think this is important enough to actually make it happen. The idea would be to enable some things with minimal effort. I’m exploring this area and there’s a half-dozen ways to make it happen, some difficult and some less so.
VISUAL STUDIO FOR MAC MANAGE NUGET PACKAGES HOW TO
A better title would be “ How to Cobble Together NuGet Support for Visual Studio 2008 with External Tools and a Prayer.” The point is, there are lots of folks using Visual Studio 2008 who would like NuGet support.
0 kommentar(er)
