The applications I work on are usually too complex to fit into a "skeleton". However when working on Winforms, I like to take advantage of CAB for the UI. I wouldn't say this is the skeleton, but more or less the ground work for which the skeleton can be built, then the meat can be built upon it. I also like using a MVC for connecting the UI to the Data Layer. The Data Layer is typically LLBLGen or nHibernate.
For generating your skeleton for web applications, the ASP.NET Dynamic Data framework looks really promising.
I just use my own class library, which handles things like SQL (differences between different engines), provides lots of custom data structures and types, IoC/Dependency injection, etc.
I have been using the XPO-library from DevExpress before but after having some rather largish performance problems with it I'm back to plain SQL.
I have never used a bigger framework like those you mention. Earlier experience with those have always led me to believe they're powerful, but also restricting. You usually end up combating the way they do things to implement more complex features.
I used CSLA.NET to build an large LOB Windows application (title insurance) in 2007, basically it is a framework that you build your business objects based on. The business objects are generated from database tables with predefined templates. SPs are mostly utilized for data access. Personally I've not liked it because there are lots of code and template need to maintain, I prefer ORM to template based approach.
I've been using XAF to build another Windows based HR application, it can help you create a complete application just in 15 minutes with nice UI and lots of cool stuffs such at localization, customization, skinable and so on. But the big problems with XAF are limitation of the underlying XPO, and not so good performance.
发布评论
评论（3）
.NET 是我最喜欢的框架。
我所从事的应用程序通常过于复杂，无法融入“骨架”中。 然而，在使用 Winforms 时，我喜欢利用 CAB用户界面。 我不会说这是骨架，但或多或少是可以构建骨架的基础工作，然后可以在其上构建肉。 我还喜欢使用 MVC 将 UI 连接到数据层。 数据层通常是 LLBLGen 或 nHibernate。
为了生成 Web 应用程序的骨架，ASP.NET 动态数据 框架看起来非常有前途。
.NET is my favorite framework.
The applications I work on are usually too complex to fit into a "skeleton". However when working on Winforms, I like to take advantage of CAB for the UI. I wouldn't say this is the skeleton, but more or less the ground work for which the skeleton can be built, then the meat can be built upon it. I also like using a MVC for connecting the UI to the Data Layer. The Data Layer is typically LLBLGen or nHibernate.
For generating your skeleton for web applications, the ASP.NET Dynamic Data framework looks really promising.
我只是使用我自己的类库，它处理诸如 SQL（不同引擎之间的差异）之类的事情，提供大量自定义数据结构和类型、IoC/依赖注入等。
我之前一直在使用 DevExpress 的 XPO 库，但在使用之后一些相当大的性能问题我又回到了普通的 SQL。
我从来没有使用过像你提到的那样更大的框架。 早期的经验一直让我相信它们很强大，但也有限制。 通常，您最终会与他们的工作方式进行斗争以实现更复杂的功能。
I just use my own class library, which handles things like SQL (differences between different engines), provides lots of custom data structures and types, IoC/Dependency injection, etc.
I have been using the XPO-library from DevExpress before but after having some rather largish performance problems with it I'm back to plain SQL.
I have never used a bigger framework like those you mention. Earlier experience with those have always led me to believe they're powerful, but also restricting. You usually end up combating the way they do things to implement more complex features.
我在 2007 年使用 CSLA.NET 构建了一个大型 LOB Windows 应用程序（产权保险），基本上它是一个构建业务对象的框架。 业务对象是根据具有预定义模板的数据库表生成的。 SP 主要用于数据访问。 就我个人而言，我不喜欢它，因为有很多代码和模板需要维护，我更喜欢 ORM 而不是基于模板的方法。
我一直在使用 XAF 构建另一个基于 Windows 的 HR 应用程序，它可以帮助您在 15 分钟内创建一个完整的应用程序，具有漂亮的 UI 和许多很酷的东西，例如本地化、自定义、可换肤等。 但XAF最大的问题是底层XPO的限制，而且性能不太好。
I used CSLA.NET to build an large LOB Windows application (title insurance) in 2007, basically it is a framework that you build your business objects based on. The business objects are generated from database tables with predefined templates. SPs are mostly utilized for data access. Personally I've not liked it because there are lots of code and template need to maintain, I prefer ORM to template based approach.
I've been using XAF to build another Windows based HR application, it can help you create a complete application just in 15 minutes with nice UI and lots of cool stuffs such at localization, customization, skinable and so on. But the big problems with XAF are limitation of the underlying XPO, and not so good performance.