RSSAmplifier

Blog

Practical Engineer - Engineering for the AI era

AI writes code in seconds. Making it reliable takes engineering. Architecture, testing, decomposition, and domain modelling |from AI chaos to shipped applications.

jonhilton.netRSS feed ↗230 posts

Latest posts

Schematrons

So what’s it all about?

WatiN

Scott Guthrie’s Blog

Rhino Mocks

Test Driven Development

The .net Framework

Web Client Software Factory 1.1 Released

Visual Studio 2008

Resharper

Upgrading to Visual Studio 2008

ASP.NET process identity does not have read permissions to the global assembly cache

Nmock Gotcha about Reference Parameters

Visual Studio Hotfix rollup

Subsonic

Shocking Gotcha – ASP.NET user controls not being referenced

Log4Net Custom Appender

Code 39 Mod 43 Checksum

'Model *View* Controller'

Abstracting your Dependency Injection framework

ASP.NET MVC Custom Controls

ASP.NET MVC Test Framework integration

MVC and good software design

MVC LINQ and OOP

'Domain Driven Design: Thought of the day'

ASP.NET and JQuery MVC Menu Part 1

ASP.NET and JQuery MVC Menu Part 2

Fluent NHibernate Gotcha

'S#arp Architecture WCF Gotcha'

BDD with MSpec and Rhino Auto Mocks (part 1)

BDD with MSpec and Rhino Auto Mocks (part 2)

BDD with MSpec and Rhino Auto Mocks (part 3)

MSpec AutoMocking

Posting an Array of Complex types using JQuery, JSON to ASP.NET MVC

Upgrading to ASP.NET MVC 2/.net 4

ASP.NET and JQuery MVC Menu Part 3 (AJAX)

Azure Local Deployment Service Channel Faulted

Rendering razor templates on the fly

'Azure Bites: API App'

So what's an API App? Well it's exactly what you think, a way of hosting an API written in your language of choice which can be scaled, secured and documented. Let's get started by creating a brand new API via the Azure Preview Portal.

'Azure Bites: Subscriptions'

So you've started using Azure and you're blown away by all the power now resting at your fingertips. One thing you probably want to keep an eye on is cost. Let's find out how to manage your Azure subscriptions.

AzureCon

In September Microsoft hosted AzureCon, a free virtual event to showcase some of the existing and new features coming to Azure.

'Azure Bites: Get your site hosted on Azure for free in 15 minutes or less'

Did you know you can host your web sites for free on Azure? Find out how to get your site up on Azure in 15 minutes or so.

'Azure Bites: Microservices in Azure'

It seems everyone is talking about them. You want to build scalable reliable software where each component can be considered in isolation and called asynchronously. How does Service Fabric help you create a microservices architecture?

How (not) to send emails from your web site – The Problem (Part 1)

A few years ago I was working on a project where we needed to add email functionality to a web site. You know the drill, a customer fills in their details on the site, clicks Contact Us and an email wings it's way to someone in the office. Read on to find out how not to do it before we look at a better solution using Azure.

How (not) to send emails from your web site – Service Bus Queues (Part 2)

In part 1 we tried (and ultimately failed) to handle customer emails using a database Now we needed to come up with an alternative.

How (not) to send emails from your web site – Topics and Subscriptions (Part 3)

So we'd got our contact us form working on the web site but now we had another requirement. The boss wanted to know how many customers were using it.

'Azure Bites: Background tasks for your web site using Azure WebJobs'

Offloading tasks to run in the background can be really useful. There are times when your users don't need to wait around for a task (such as sending an email) to finish. I recently heard about Azure webjobs and decided to give them a go. It turns out they really simplify your message consuming code and finally get rid of those pesky loops!

Why coupling will destroy your application and how to avoid it

Left unchecked, tight coupling between components (especially when distributed around your application) can slowly kill your software; rendering it hard to maintain and much more likely to suffer from bugs. How can we identify and reduce coupling in our applications?

Apply “Tell Don’t Ask” and reduce coupling

A few days ago I wrote an article on how coupling (when left unchecked) can impact your code. We looked at exceptions and considered the impact of throwing them in one part of your code, to catch them somewhere else. I had some great feedback on that post and one comment in particular regarding the viability of the delegate approach in a more realistic example. Let's remind ourselves where we…

'Reduce coupling: Free your code and your tests'

If you’ve ever tried to refactor some code only to find that your tests broke (even though you retained the same functionality) then the chances are your tests were tightly coupled to your implementation.