{"id":44,"date":"2008-05-14T15:21:00","date_gmt":"2008-05-14T20:21:00","guid":{"rendered":"http:\/\/www.dontpapanic.com\/blog\/?p=44"},"modified":"2008-05-14T15:21:00","modified_gmt":"2008-05-14T20:21:00","slug":"adding-useful-visual-studio-external-tools","status":"publish","type":"post","link":"https:\/\/www.dontpapanic.com\/blog\/?p=44","title":{"rendered":"Adding Useful Visual Studio External Tools"},"content":{"rendered":"
\n
\n

We add a couple of External Tools to our Visual Studio 2005 environment when teaching SharePoint classes to simplify some two common tasks encountered when developing for SharePoint.  The first tool generates a unique Globally Unique Identifier<\/strong> (GUID) and places it in your clipboard so that you can paste it directly into Features or Solution manifests.  The other tool can retrieive the Public Key BLOB and Token from a signed dll so that you can use them in custom webpart or dwp files, safe control entries, or custom code access security policies.  Integrating these tools into the menu of Visual Studio makes using them much more convenient than the command line alternatives.<\/p>\n

Recently a student asked for a step by step guide to adding these external tools so they can add them to their own development environment.  Rather than simply respond back to them by email I thought it would be worthwhile to document the steps here for others who might also be interested.<\/p>\n

Implementing guidgen.exe<\/u><\/strong><\/p>\n

    \n
  1. Select External Tools<\/strong> from the Tools<\/strong> menu in Visual Studio 2005. <\/li>\n
  2. Click Add<\/strong> to add a new external tool to the menu.  You will see the following dialog box.
    \n

    \"External<\/a><\/p>\n<\/li>\n

  3. \n

    Fill in the following:
         C&reate GUID<\/strong> for Title
    <\/em>     C:\\Program Files\\Microsoft Visual Studio 8\\Common7\\Tools\\guidgen.exe <\/strong>for Command<\/em>
         C:\\Program Files\\Microsoft Visual Studio 8\\Common7\\Tools<\/strong> for Initial directory<\/em><\/p>\n<\/li>\n

  4. Click OK<\/strong> to save the new menu entry. <\/li>\n
  5. Select Cr<\/u>eate GUID<\/strong> from the Tools<\/strong> menu and you will see the following dialog:
    \n

    \"Create<\/a> <\/p>\n<\/li>\n

  6. Be sure to select GUID Format #4, Click the N<\/u>ew GUID<\/strong> button, and then the C<\/u>opy<\/strong> button.  The GUID is now in your clipboard paste buffer.  <\/li>\n
  7. Ex<\/u>it<\/strong> the tool and paste your GUID into Visual Studio.  (Note: be sure to remove the braces from the outside of the GUID since they aren’t needed.) <\/li>\n<\/ol>\n

    Implementing SN.exe<\/u><\/strong><\/p>\n

      \n
    1. Select External Tools<\/strong> from the Tools<\/strong> menu in Visual Studio 2005. <\/li>\n
    2. Click Add<\/strong> to add a new external tool to the menu.  You will see the following dialog box. <\/li>\n
    3. Fill in the following:
           &Get Token<\/strong> for Title
      <\/em>     C:\\Program Files\\Microsoft Visual Studio 8\\SDK\\v2.0\\Bin\\sn.exe <\/strong>for Command<\/em>
           -Tp "$(TargetPath)"<\/strong> for Arguments<\/em> <\/li>\n
    4. Select the Use Output Window<\/strong> checkbox <\/li>\n
    5. Click OK<\/strong> to save the new menu entry. <\/li>\n
    6. Once you’ve built your project select G<\/u>et Token<\/strong> from the Tools<\/strong> menu while one of your code files is open in the code editor and you will see something like the following in your Output Window:
      \n

      \"Output<\/a><\/p>\n<\/li>\n

    7. You can now highlight and copy either the Public key token or the Public key BLOB for use in your code. <\/li>\n<\/ol><\/div>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

      We add a couple of External Tools to our Visual Studio 2005 environment when teaching SharePoint classes to simplify some two common tasks encountered when developing for SharePoint.  The first tool generates a unique Globally Unique Identifier (GUID) and places it in your clipboard so that you can paste it directly into Features or Solution … Continue reading Adding Useful Visual Studio External Tools<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[19,15,23],"class_list":["post-44","post","type-post","status-publish","format-standard","hentry","category-sharepoint-2007-dev","tag-development","tag-sharepoint_2007","tag-tips"],"_links":{"self":[{"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/44","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=44"}],"version-history":[{"count":0,"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/44\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=44"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=44"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dontpapanic.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=44"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}