Platform

Morphfolia is an ASP.NET based application; it is purpose built purely to provide a platform for the development of ASP.NET web sites and web applications.

The currently supported version of the .Net framework is v2.0, with plans to upgrade to v3.5 (or higher) at some stage in the future.

Morphfolia was developed on Microsoft XP Professional, no extensive or specific testing has been done on any other platform, however, several instances of Morphfolia run successfully on local ISP's (the oldest has been operational for around three years).

The database platform is MS SQL 2005, with plans to upgrade to SQL 2008 at some point (hopefully this year). The data access tier of Morphfolia is abstracted out - a clean break between it and the business logic tier (more info on the architecture still to come); developers can implement any data provider they like, though only the SQL 2005 data provider is supplied (for now).

The SQL 2005 data provider also works with SQL 2000 (or it should.  The database is fairly straight forward - no complex extensions.  The current database architecture worked under SQL 2000 until a few months ago, and since then there have only been minor changes).

Technologies

ASP.NET MVC

Morphfolia is a 'classic' (?) ASP.NET application, not an MVC one, however, Morphfolia is deliberately architected around the use of HTTP Handlers - which are central to the MVC Framework; as such Morphfolia enjoys some of the same advantages as the ASP.NET MVC framework:

• The ASP.NET MVC allows gives you total control over the response (i.e: the HTML) sent to the browser, so does Morphfolia as you can develop your own HTTP Handlers (or copy and modify existing ones) to provide any response you want.
• Like the ASP.NET Framework, Morphfolia offers many points for extensibility.  I can't speak authoratively for the MVC framework as I haven't used it in depth, however, the ability to meet different requests with different responses is completely open to you.  You can use the HTTP Handlers (and the related Page Layout templates and Skin providers), write your own, or use the 'standard' Microsoft ASP.NET HTTP Handler that provides the normal ASP.NET WebForm functionality we're all familiar with - therefore Morphfolia allows you to provide 'classic' and MVC like behaviour in the same solution.

jQuery

Morphfolia doesn't use any third party JavaScript Libraries (not even the Microsoft AJAX ones - although that may change in the future as I look to increase performance and efficiency in teh Admin section), so jQuery isn't used out of the box.  This is in keeping with the design goal of keeping 'out-of-the-box' dependancies to an absolute minimum.  By using Page Layouts you can include references to JavaScript resources and libraries that embelish your application.

Got a question about what is or isn't used?  Contact me.