Wet looking for a decent error logging system. found one:
My next project will be a first for me, being a 100% web, stand-alone portal/application. Here’s my current thinking on its makeup
- SQL Server back-end. This project will go live prior to Azure web services going live so SQL Server 2008 it is.
- ActiveRecord with ActiveWriter. I’ve used these two extensively for the last five months on a client project. Both me and the client have loved the rapid development on offer for such a small investment in learning time. ActiveWriter isn’t flexible enough to support the attributing I’ll need so I’m going to have to do some work on its codebase to allow arbitrary attributes. Man, those classes and properties are going to be attribute-heavy!
- IIS7 and .NET 3.5. My hosting provider provides this and I’ve been building web services on this platform for a while.
- ASP.NET MVC for the ‘web application’ side of things. I’m test driven, can write reasonable HTML and haven’t spent two years (Hi Ollie Venn) learning all the gotchas inherent in WebForms.
- JQuery- you know it makes sense given the above.
- Umbraco – the only content management system I’ve wished I had designed.
- UnFuddle – I’ve been using this as a bug tracking system for a while, and the Agile side of it looks agile enough for me.
Maybe I’m putting the tech before the requirements here, but I control both to a large extent so I can do as I please.
The project kicks off when I get back from the MVP Summit (2nd week of March IOW), and I’ll be blogging here about how I get on, starting with the ActiveWriter modifications.