Map the Caps Lock key on your Surface Pro 3 to be the Insert Key

I have really missed the Insert key on my Surface Pro 3 (SP3).  In the process of searching for a key combination that replaced it, I learned that there wasn’t one.  Scott Hanselman posted how to remap the Insert key using SharpKeys.  This utility makes it really simple to make the change.

However, I was also curious about how to remap it by adding a value to the Windows Registry.  After reading about this on the Softpanorama web site, I found that I simply had to do the following:

    1. Go to Start->Run (or press Win+R) and type in ‘regedit’ to open the registry editor.
    2. Navigate to:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout
      Note: Keyboard Layout, not Keyboard Layouts!

    3. Go to Edit->New->Binary Value and name it ‘Scancode Map’
    4. Now double-click and edit the value to the following:

      00 00 00 00 00 00 00 00 02 00 00 00 52 E0 3a 00 00 00 00 00

      Note that the 52 E0 represents the scan code for the Caps Lock key.

    5. Now log off and back in.  Pressing the Caps Lock key will now behave like the Insert key.
      1. If logging off and back in doesn’t affect the change, reboot your machine.

Thanks to Softpanorama for such a great post!

Rob

This post was migrated from https://blogs.msdn.microsoft.com/rob/2015/03/04/map-the-caps-lock-key-on-your-surface-pro-3-to-be-the-insert-key/.

Viewing All of the Git Repositories in your TFS Team Project within Visual Studio 2013.3

I recently reconnected to a TFS 2013.3 Team Project after quite a while away.  I knew that additional Git repos had been added to the team project, but Visual Studio 2013.3 was not displaying them in Team Explorer.  It turns out that you need to click the Refresh button (see the red rectangle, below) to update the list of Git repos.  Once you do this, you can see (and thus clone) any of the existing repos.

HTH

Rob

This post was migrated from https://blogs.msdn.microsoft.com/rob/2014/10/27/viewing-all-of-the-git-repositories-in-your-tfs-team-project-within-visual-studio-2013-3/.

Chocolatey Tip of the Day: cup all

If you use Chocolatey (http://chocolatey.org/) and you want to update all of the packages you already have installed, just enter the following at the command prompt and all will be updated:

cup all

If you don’t want to be prompted for confirmation for each package, then enter the following instead:

cup -y all

Rob

This post was migrated from https://blogs.msdn.microsoft.com/rob/2014/05/18/chocolatey-tip-of-the-day-cup-all/.

Fixing “The ‘CctSharedPackage’ package did not load correctly”

I started Visual Studio 2013 this morning and opened the About dialog to make sure that I was running Update 1 on this particular machine.  Before the About dialog was displayed, I got the following error dialog:

---------------------------
Microsoft Visual Studio
---------------------------
The 'CctSharedPackage' package did not load correctly.

The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file 'C:\Users\...\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml'.

Continue to show this error message?
---------------------------
Yes   No   
---------------------------

Ack!  What happened?  Apparently this is an issue with the Windows Azure Tools for Microsoft Visual Studio 2013 – v2.2.  Although further research shows that it’s a problem with previous versions of the Azure SDK, as well.  So, I went to Control Panel, opened “Programs and Features”, right-clicked on “Windows Azure Tools for Microsoft Visual Studio 2013 – v2.2”, and clicked “Change”.  In the “Modify Setup” dialog that appeared and clicked “Repair”.  This fixed the problem.

Rob

This post was migrated from https://blogs.msdn.microsoft.com/rob/2014/02/12/fixing-the-cctsharedpackage-package-did-not-load-correctly/.

Connect Windows Live Writer to Your MSDN Blog

This is just a quick reminder post for me (or someone else who stumbles across this) that the solution to connecting your MSDN blog to Windows Live Writer can be found here:

http://blogs.msdn.com/b/ajay_pathak/archive/2012/01/02/now-write-blogs-on-msdn-via-windows-live-writer.aspx

Note the following:

  1. The Settings URL did not take me to my account settings.  I had to log into my account and then go to the Settings page on http://blogs.msdn.com.
  2. The login to allow 3rd party application access to your MSDN blog, e.g. Windows Live Writer, does not use your Microsoft Account password.  There is a separate password, which is what you are requesting to change.
  3. Although my outlook.com address is what I use to log into my MSDN blog, it still wanted my Hotmail.com address to log in with Windows Live Writer.

Rob

This post was migrated from https://blogs.msdn.microsoft.com/rob/2014/01/19/connect-windows-live-writer-to-your-msdn-blog/.

Load more