新 Asp.net CMS 站点的 Oxite 或 S#arp 架构
我想构建一个基于 Asp.Net Mvc 的 CMS 网站，并且我想选择我的起点。
我发现人们对新的 Microsoft Oxite 项目很感兴趣，而且在生产项目中采用它似乎还为时过早。
我还研究了 S#arp 架构，但它与 Oxite 相比并不合适，因为 Oxite 只是一般 Asp.Net Mvc 站点的起点。
对我来说，S#arp 架构比 Oxite 有一些优势，因为它的复杂性要低得多，并且它使用 Nhibernate 作为数据访问层。
Oxite 代码使用 Linq2Sql 作为 DAL，并且解决方案中已经有一个项目需要 VS2008 的 DB 版本。
在我看来，Oxite 似乎更面向博客而不是面向 CMS，但我还没有深入查看代码。
以下是一些将我引向 S#arp Ar 的选择。 开始。
- 简单干净的架构
- Nhibernate Dal
- 社区支持
Oxite：
- 微软项目
- 潜在的巨大社区
- 早期阶段，但代码质量非常好
- 提供者模型，允许轻松切换 DAL
如果有人看过这两个项目的代码，请提出您的意见。
谢谢
I'd like to build a CMS site based on Asp.Net Mvc and I want to choose my starting point.
I have seen that there is a lot of interest in the new Microsoft Oxite project also if it seems to be pretty early to adopt it in a production project.
I've also looked at S#arp Architecture but it does not properly compare to Oxite as is just a starting point for general Asp.Net Mvc sites.
For me S#arp Architecture has some advantages over Oxite as is far less complex and it uses Nhibernate for the data access layer.
Oxite code uses Linq2Sql for it's DAL and has already a project in the solution that requires the DB version for VS2008.
Oxite seems to me more blog oriented than CMS oriented but I haven’t looked the code deeply.
Here are some of the choices that would point me to S#arp Ar. for starting.
- Simple clean architecture
- Nhibernate Dal
- Community supported
Oxite:
- Microsoft project
- Potential huge community
- Early stages but very good code quality
- Provider model that permits to easily switch the DAL
If anyone has looked at the code of these two projects please advice on your opinions.
Thanks
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我在 SO 上关于 Oxite 的问题没有得到太多答复（可在 Oxite：你打算用它做什么？），但它确实很新，所以人们需要一些时间来熟悉它并全面检查它。 Oxite 的架构非常容易上手； 这是它的最强项。
在阅读你的问题之前，我从未听说过 S#arp，所以我一定会检查一下。
I didn't get much of a response at my question about Oxite here at SO (found at Oxite: What are you going to do with it?), but it is really new so it'll take some time for people to warm up to it and fully check it out. The architecture of Oxite is really easy to get started with; that's its strongest suit.
I'd never heard of S#arp before I read your question so I'll definitely check it out.
Oxite 已经很详细了，完全是负面的。
我只想补充一点，我已经使用 S#arp 架构 几个月了，发现它非常易于维护和灵活。 围绕它还有一个非常稳固、不断增长且活跃的用户社区。
它非常干净，并且很容易升级到 Fluent NHibernate RC 1.0
Oxite is well detailed already, entirely negatively.
I'll just add that I've been using S#arp architecture for several months and found it very maintainable and flexible. There's also a very solid, growing and active community of users around it.
It is very clean, and quite easily upgraded to Fluent NHibernate RC 1.0
Oxite 可能功能丰富，但代码质量非常低。
当我检查代码并发现控制器操作包含 100 多行非常不干净的代码、tagoup 视图、没有单元测试等时，我感到非常惊讶。
这些批评已经在这些博客文章中得到了很好的总结：
http://blog.wekeroad.com/blog/some-thoughts-on-oxite/
http://codebetter. com/blogs/karlseguin/archive/2008/12/15/oxite-oh-dear-lord-why.aspx
Oxite might be feature rich, but the code quality is very low.
I was very surprised when I checkout the code and found controller actions with 100+ lines of very unclean code, tagsoup views, no unit tests, etc.
The criticism has been well summed up in these blog posts:
http://blog.wekeroad.com/blog/some-thoughts-on-oxite/
http://codebetter.com/blogs/karlseguin/archive/2008/12/15/oxite-oh-dear-lord-why.aspx
一如既往，这取决于您的需求。 听起来您需要更多基于 CMS 的东西。 Oxite 恰好具有一些类似 CMS 的功能，但它并不是真正的 CMS。 它可能是在未来，因为它是一个社区项目，但现在它不是（您所能做的就是添加内容页面）。
我们很高兴每个人似乎总体上都喜欢 Oxite，但现在还为时过早。 不是为了阻止任何人在生产中使用它，因为我们就是这么做的。 我们在其上运行 MIX Online，但如果您对此感到不舒服，我们完全理解。 我们需要一个稳定期。 同时我们还需要有人来运行它，这样我们才能使其稳定。 我会说先有鸡还是先有蛋。 :)
As always, it depends on your needs. It sounds like you need something more CMS based. Oxite happens to have some CMS-like features, but it's not really a CMS. It might be in the future as it's a community project, but right now it isn't (all you can do is add content pages).
We're glad everyone seems to like Oxite overall, but it is pretty early. Not to deter anyone from using it in production, because we do. We run MIX Online on it, but totally understand if you're not comfortable with it. We need a stabilization period. At the same time we also need people running it so we can make it stable. Chicken and Egg I'd say. :)