OK, it’s not true yet, but it will be…
I’ve decided to live by the phrase
Eat your own dog food
and switch my personal site over to Mono. I can hardly go around extolling the virtues of Mono for web applications when I run a PHP-based CMS can I?
Of course it is very early days yet, and I’ve got a long way to go before I can replace Textpattern fully. What I can do though is re-implement the presentation layer, so that is where I have started…
Show me something!
After some experimentation today. I have now got an ASP.NET page up and running that talks to my MySQL database that stores the Textpattern data. You can view it here – go try it out!
Update
I’ve revised the page somewhat, blending it with the rest of my site, adding more information and changing controls.
Decisions, decisions
I’m not sure whether I’ll remain with MySQL – PostgreSQL provides the features (Stored Procedures, Triggers) that I’m already used to developing with/for on MS SQL – it seems stupid to me to go back to building SQL statements on the fly. I know MySQL has/will have these, but PostgreSQL has them now.
Besides, if I make that switch I can keep the LAMP acronym – it will just mean Linux Apache Mono PostgreSQL instead of Linux Apache MySQL PHP/Python/Perl. 
Fascinating :)<br />
I appreciate that this is a go-away-and-rtfm question for me, but: why is the list of titles enclosed in a form? It’s not a form.
Another great alternative lamp
FYI my sig is “Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL”
Look forward to seeing you Mono-Powered soon! Dog food is good. I think you’ve hit the nail on the head regarding PostgreSQL as a great replacement for SQL Server. We have a few open source .NET apps running on variations of Linux / Apache / Mono / PostgreSQL over at gotmono.net that you may find useful.