Well, yesterday I decided to find out how much it would cost to add a SQL database to my hosting account at SecureMate. Again, they blew me away with their service. Within 15 minutes I’d got their reply… it took less than 30 minutes for the whole thing to be setup. Why would I want an SQL database? Because now I can run .Text or other blogging systems (like dasBlog) Also, it means that I can actually do something with my site that would look vaguely professional… except for the minor fact that I “don’t do pretty”, but at least it would be technologically professional. Well, maybe not… but at least I would have the potential to have do more on the site. I read an interesting article on TheServerSide.Net yesterday. As an aside: TheServerSide.Net site was launched yesterday and looks like it could be excellent, it generated a fair bit of interest in the blog sphere yesterday, check out Julia’s comment for a start. Anway, the “inaugural” message from the editor made some interesting comments. I often wonder how anyone is meant to build a “best practice” application, when often the technology is not fully understood. I’ve tried to grasp it completely before I confidently move forwards, but that seems rather unlikely to happen quickly – especially with a technology that’s shifted development mindsets as much as .Net has. He comments:
.NET introduces a huge new learning curve to the Microsoft technology developer. Just take a look at the list of namespaces in the MSDN documentation. It’s huge – well over 60 namespaces alone, with even more promised as part of the Whidbey release. And, of course, each of those namespaces in turn contains classes, each of which in turn contains properties, methods, and events, all of which somehow collaborate to create the .NET Base Class Library and related functionality. That still doesn’t even take into account the intricacies of the CLR itself, nor the various technology bases that some of the .NET libraries touch, such as the relational database, the underlying windowing system encapsulated by WinForms, HTTP and the Web, or XML and/or XML-based Web Services. It’s a huge space we’re contemplating, and there’s a lot of lessons to be learned about what to do – and what not to do – when building enterprise .NET applications. [ … ] The truth is, even though the last 3 years of my life have been spent teaching and speaking and researching .NET alongside some of the brightest .NET experts in the world, I can’t claim to “know” how to build .NET enterprise applications. Nobody can, at least not without a serious disclaimer attached.Finally someone’s said what my mind was only begining to think about grasping.