{"id":56207,"date":"2013-07-25T00:00:00","date_gmt":"2013-07-25T07:00:00","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/nuget\/invoke-manage-nuget-packages-dialog-programmatically"},"modified":"2013-07-25T00:00:00","modified_gmt":"2013-07-25T07:00:00","slug":"invoke-manage-nuget-packages-dialog-programmatically","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/invoke-manage-nuget-packages-dialog-programmatically\/","title":{"rendered":"Invoke the Manage NuGet Packages dialog programmatically"},"content":{"rendered":"

Recently I’ve been asked several times for how to invoke the Manage NuGet Packages dialog from VS components programmatically, and optionally auto-invoke the search when the dialog opens. Today I’d like to share the solution in this post.<\/p>\n

It’s actually very straightforward. The Manage NuGet Packages<\/strong> menu command is registered as a standard VS command, thus you can call DTE.ExecuteCommand()<\/code> to invoke it. The trick is to know the command name, which is Project.ManageNuGetPackages<\/strong>. Here’s a code sample:<\/p>\n

DTE dte = (DTE)GetService(typeof(SDTE)); \ndte.ExecuteCommand(\"Project.ManageNuGetPackages\");<\/code><\/pre>\n
Note that it will open the project-level<\/em> dialog. To open the solution-level<\/em> dialog instead, you replace the command name with Tools.ManageNuGetPackagesforSolution<\/strong>.<\/p>\n
The ExecuteCommand()<\/code> method also accepts a second optional parameter of string type. If you pass a string value to it, the NuGet command handler will intepret it as a search query and will automatically issue a search request after it has opened the dialog.<\/p>\n
DTE dte = (DTE)GetService(typeof(SDTE)); \ndte.ExecuteCommand(\"Project.ManageNuGetPackages\", \"jQuery\");<\/code><\/pre>\n
With the above code, assuming you have the Online tab selected the last time you closed it, you will see this:<\/p>\n
\"Dialog<\/p>\n
If, for some reason, you don’t like to call through DTE, you can also invoke the command directly through the OleMenuCommandService<\/code> service.<\/p>\n
var nugetCommandGuid = Guid.Parse(\"25fd982b-8cae-4cbd-a440-e03ffccde106\"); \nvar nugetCommand = new CommandID(nugetCommandGuid, 0x100); \n\n\/\/ 0x100 is the command id for project-level dialog \nOleMenuCommandService mcs = GetService(typeof(IMenuCommandService)) as OleMenuCommandService; \nmcs.GlobalInvoke(nugetCommand, \"jQuery\");<\/code><\/pre>\n
Again, to open the solution-level dialog, you set the command id to 0x200. These constants are set in the NuGet source code<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Recently I’ve been asked several times for how to invoke the Manage NuGet Packages dialog from VS components programmatically, and optionally auto-invoke the search when the dialog opens. Today I’d like to share the solution in this post. It’s actually very straightforward. The Manage NuGet Packages menu command is registered as a standard VS command, […]<\/p>\n","protected":false},"author":4268,"featured_media":58792,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[7874,646],"tags":[],"class_list":["post-56207","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-nuget","category-visual-studio"],"acf":[],"blog_post_summary":"
Recently I’ve been asked several times for how to invoke the Manage NuGet Packages dialog from VS components programmatically, and optionally auto-invoke the search when the dialog opens. Today I’d like to share the solution in this post. It’s actually very straightforward. The Manage NuGet Packages menu command is registered as a standard VS command, […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/56207","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/4268"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=56207"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/56207\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=56207"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=56207"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=56207"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}