What structure do you use to build your applications?
.NET is my favorite framework.
The applications I work on are usually too complex to fit into a skeleton. However, while working on Winforms I like to use the CAB for the UI. I would not say that this is a skeleton, but more or less earthworks, for which a skeleton can be built, then meat can be built on it. I also like to use MVC to connect the UI to the data layer. The data layer is usually LLBLGen or nHibernate.
For building your skeleton for web applications, the ASP.NET Dynamic Data framework looks very promising.
source to share
I'm just using my own class library that handles things like SQL (differences between different engines), provides many custom data structures and types, IoC / Dependency injection, etc.
I've been using the XPO library from DevExpress before, but after some pretty big performance issues, I've gone back to plain SQL.
I have never used a larger structure like the ones you mention. My early experience with them always made me think they were powerful, but also limiting. Usually you have to struggle with how they do things to implement more complex functionality.
source to share
I used CSLA.NET to build a large Windows LOB (Title Insurance) Application in 2007, basically this is the framework on which you build your business objects. Business objects are created from database tables with predefined templates. SPs are mainly used for data access. I personally didn't like this because there is a lot of code and template to maintain, I prefer ORM for a template based approach.
I am using XAF to create another Windows based PC application, it can help you create a complete application in just 15 minutes with a nice user interface and lots of cool stuff like localization, customization, skins, etc. But the big problems with XAF are the base XPO limitation and not very good performance.
source to share