I'm kicking off a new project - a WPF application using WCF and SQL Server, with a little ASP.NET MVC portal.
A fun part of new projects is getting to decide which technologies and libraries to use. For me, it's going to be:
- Autofac, the IOC container
- AutoMapper, for that left-hand = right-hand code
- Magellan, the navigation framework
- Moq, for mocking
- NBuilder for building test objects easily
- NHibernate and FluentNHibernate for that pesky database
- NUnit, for testing
A long-term goal for this application is to use a message bus for communication. For now, I don't want the infrastructure hassles, and it's not so important, so I'm hoping to make my code feel like I'm using a bus while really using point-to-point WCF. I was hoping to use Agatha, which makes WCF feel more like a messaging layer, but it would have introduced a third logging library that I just don't care for. Perhaps I'll fork the code or just borrow the ideas and write my own.
The ASP.NET MVC app will probably use the default ASP.NET view engine, but I'll switch to Razor if they ever release it.
For database management, I'm planning to use the same database deployment tool that I use for managing my blog. I just can't stand DataDude.
It's interesting to look on this list and compare it to what it might have been a few years ago. There's no trace of patterns & practices, and no third party control libraries - and especially no data grids :)
What does the lib folder on your current project look like?
Enjoying these posts? Subscribe for moreSubscribe now
Already have an account? Sign in
Hello, I'm Paul Stovell
I'm a Brisbane-based software developer, and founder of Octopus Deploy, a DevOps automation software company. This is my personal blog where I write about my journey with Octopus and software development.
I write new blog posts about once a month. Subscribe and I'll send you an email when I publish something new.Subscribe