Posts

Generate SQL Statements to Group By Each Column of Table Separately

When working with data with the intent to visualize, there are times when I'll want to group by every column in a table, separately, one at a time, to determine the possible values in that column. I do this often enough I created a simple SQL Query to build these group by statements for me: declare @table_name varchar(200) = 'dbo.mytablename' select 'select ' + c.name + ', count(1) cnt from ' + @table_name + ' group by ' + c.name + ' order by 2 ' from sys.columns c where c.object_id = object_id(@table_name) gist:  https://gist.github.com/aaronhoffman/d49d3705fd716b0fe6cb Hope this helps, Aaron

ASP.NET MVC 5 Identity, Users, Roles, Accounts, SQL to Generate Tables

In ASP.NET MVC 5, user management changed significantly from ASP.NET MVC 4. This is the start of a series of blog posts on the topic (long overdue). This post is on the SQL that your website executes to initially create the identity (user, role) tables. The SQL the ApplicationUserManager and ApplicationSigninManager generate and execute is below: CREATE TABLE [dbo].[AspNetRoles] (     [Id] [nvarchar](128) NOT NULL,     [Name] [nvarchar](256) NOT NULL,     CONSTRAINT [PK_dbo.AspNetRoles] PRIMARY KEY ([Id]) ) go CREATE TABLE [dbo].[AspNetUserRoles] (     [UserId] [nvarchar](128) NOT NULL,     [RoleId] [nvarchar](128) NOT NULL,     CONSTRAINT [PK_dbo.AspNetUserRoles] PRIMARY KEY ([UserId], [RoleId]) ) go CREATE TABLE [dbo].[AspNetUsers] (     [Id] [nvarchar](128) NOT NULL,     [Email] [nvarchar](256),     [EmailConfirmed] [bit] NOT NULL,     [PasswordHash] [nvarchar](max),     [SecurityStamp] [nvarchar](max),     [PhoneNumber] [nvarchar](max),     [PhoneNumber

Install and Setup Windows 10 for a Developer

Image
I have been writing code on the Microsoft Stack for around 10 years and have set up quite a few developer machines over the years. Starting with Windows XP, Visual Studio 2003, and SQL Server 2000, and on every version of Windows, VS, .NET, and SQL Server since. If there is a quirk with installing dev tools, I've likely run into it. I recently upgraded my primary dev machine to Windows 10, Visual Studio Enterprise 2015, and SQL Server 2014, and decided to capture the steps in this blog so I could point other people to it. Notice: Obviously, these are my preferences, and may not work for your situation. I am writing this post after running this setup for about a week* (edit: about 6 months now and still good). I will update this post as I continue to work with Windows 10. Objective From scratch, set up a developer machine with the following: 1. Windows 10 Pro 2. SQL Server 2014 Developer Edition 3. Visual Studio 2015 Enterprise Edition 4. Other dev tools (git, Sublime Tex

Import-Module The specified module OneGet was not loaded because no valid module file was found in any module directory

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

AutoHotKey Mac Keyboard on Windows 8

Image
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