Deploying ASP.NET MVC 3 Razor Web App to AppHarbor < 4 Minutes

Of all the cloud providers out there, AppHarbor easily provides the smoothest deployment experience for .NET available today. I did this in one shot, including a few mistypes, and still deployed an ASP.NET MVC 3 Web Application to AppHarbor in 3 minutes and 50 seconds.  (Be sure to hit the HD button in the top right corner to get the higher definition video)

Also cross posted on Youtube.

Infrastructure Updates

A few updates on the infrastructure project I’ve been putting together on at github/infrastructure.

Javascript Enabling TDD

First steps toward enabling TDD Javascript by adding QUnit.  Now that the framework is available, I’ll have it added to the next template update.

Globalization

I will at some point have a blog entry put together and published on how I put this together.  It is a simple implementation of globalization, and will also be in the next template version.

Fizzware NBuilder, CSS Templates, NHibernate, FluentMigrator, and other bits

These parts have been added via Nuget, however, I haven’t determined the ideal way to include the includes (see what I did there!).  For the next template though, I’m going to make a command decision and have that implemented for the template.  Either a scripted Nuget install, inclusion of the assemblies, or otherwise.

A Few WTF Moments!

Ever been working along on something, and you see an ad or get an error that just boggles the mind?  You look at it and just think to yourself, “what the…  why did they… I…  don’t… can’t…  even…  imagine.  Ugh idiot!”  Well here’s a few that have hit me lately.

This is SUPPOSED to be the Free Tier?

This is SUPPOSED to be the Free Tier?

I know, really, NOT a big deal at all.  1 penny.  But seriously, it’s supposed to be the free tier.  It probably cost MORE to charge 1 penny against my credit card than to just fix the mistake.  Meh, whatever, it’s rather hilarious really.

When The Hell Did This Get Updated Last??!?!?!

When The Hell Did This Get Updated Last??!?!?!

I got nuthin’.  Seriously, this is inexcusable for a corporate environment.  How many other security protocols or other things are completely in disrepair?  This type of nonsense actually concerns me.  (and btw, this was using Chrome, the IE message for IE 9 came up the same way)

Hosted TFS!?!? for $20 Bucks a Month?

Hosted TFS!?!? for $20 Bucks a Month?

Oh dear.  It’s bad enough using TFS internally, but hosted!  I can only imagine the horror!  In addition, at $20 bucks you could have gigs upon gigs of private storage for a Git or Mercurial account.  My take, go get an Unfuddle or Repository Hosting Account and use a seriours distributed source control system.  It’s time to step away from the sourcesafe… err, I mean TFS… and use a functional, scalable, and non-hindrance prone source control system.

Hope that was entertaining.  That was my PSA (Public Service Announcement) of the week.  Enjoy.

Iteration End, Velocity++, Chart Awesomeness, Contribute Back Plz K Thx!

Here’s a few charts and such from the end of an iteration that the team I’m on just wrapped.  I’d love to see any TFS charts of this nature or other solutions in JIRA, TeamCity, or whatever is used.  Anyone else out there want to get a blog post up about it, I’ll add a link at the end of my entry here.

Lots of Tests, Good Continuous Integration Build

Lots of Tests, Good Continuous Integration Build

Gotta have solid test coverage for any reasonable expectation of maintenance.  When I mean tests, I’m talking about properly abstracted, mocked, stubbed, faked, or otherwise built so as they don’t depend on all sorts of nonsensical external dependencies like file systems, database, or other things.

Code Coverage, in general keeps an upward trend!

Code Coverage, in general keeps an upward trend!

100% is a little fanatical, but an upward trend after the beginning of a project and the initial work beginning is one of the best things to see.  Code coverage with tests means you’ll be able to get all sorts of goodies:  maintainable code, non-increasing tech debt, faster refactors, etc.

The Few Fixes Needed, Get Fixed Pretty Quick!

The Few Fixes Needed, Get Fixed Pretty Quick!

Unit test fixes.  Should be quick, should be furiously done, and shouldn’t take more than about an hour on the infrequent times they occur at all.

Unit Test Coverage Up...

Unit Test Coverage Up…

Increasing Count

Increasing Count

…and of course, the burn down.

BURN baby BURN!

Burn Down

Burn Down