Aaron Hoffman's Blog

Windows 10, PowerShell, OneGet, PackageManagement, Chocolatey You may have tried the command: Import-Module -Name OneGet And received this message: Import-Module : The specified module 'OneGet' was not loaded because no valid module file was found in any module directory. But that's okay, because OneGet was renamed to PackageManagement. So just run this instead: Import-Module -Name PackageManagement And really, you probably don't even need to run that command at all. Sources: http://www.fixedbyvonnie.com/2014/11/5-minute-setup-using-oneget-chocolatey-windows-10/   http://blogs.technet.com/b/packagemanagement/archive/2015/05/05/10-things-about-oneget-that-are-completely-different-than-you-think.aspx

I've been doing a lot of work on site recently on a MacBook Pro, and, although I resisted at first, I've grown very fond of the Mac keyboard experience (although this could be attributed to Stockholm Syndrome). At home however I still use my Dell Windows Desktop for most of my Windows/.NET development. However, to keep the keyboard experience similar between my MacBook and my Windows Desktop, I bought a Mac Keyboard with Numpad for my Desktop (because customizing a MacBook keyboard to function like Windows is more difficult/impossible, luckily the other way around is not too difficult). I then needed to modify the default behaviors slightly to better simulate the Mac keyboard experience on Windows. The main differences are with the cmd+`key` functions vs ctrl+`key` and the location of the numpad operators. I used autohotkey to customize the default behavior and it works pretty well. Instructions on how to do this are below. Setup Steps: You'll need to install autohotke...