我们应该在 DotNetNuke 平台上构建我们的下一代 Web 应用程序吗? [英] Should we build our next generation web application on the DotNetNuke platform?

问题描述

我们目前正在考虑使用 DotNetNuke 作为我们未来将集中托管的基于门户和客户端可定制的 Web 应用程序的基础.这个想法是将动态部分作为 DNN 模块，这些模块反过来与负责业务处理和数据存储的后端 WCF 服务对话.

We are currently considering using DotNetNuke as a base for our future portal-based and client-customizable web application that is going to be hosted centrally. The idea is to make the dynamic parts as DNN modules that in turn talk to backend WCF-services which takes care of the business processing and data storage.

你对这样的模型有什么好的/坏的体验?

What are your good/bad experiences with such a model?

您有什么要警告或推荐的吗?

Anything you would warn against or recommend?

任何建议将不胜感激，谢谢...

Any advice would be appreciated, thanks...

推荐答案

DotNetNuke 可以成为一个强大的平台.大多数抨击它的人实际上并没有将它用于任何事情，只是知道它是很久以前创建的.

DotNetNuke can be a powerful platform. Most people who bash it haven't actually used it for anything, but just know that it was created a long time ago.

我可以给你一些优点和缺点来看看.与其他 CMS 平台相比，使用它的主要优势在于它是一个非常成熟的平台，周围有相当大的社区(例如 Snowcovered).对于大多数任务，它要么已经内置，要么已经有人构建了一个模块来完成它.它的架构已经构建为支持高可用性应用程序的缓存和场配置，如果您正在查看大量请求，这将消除一个主要的头痛问题.

I can give you a couple pros and cons to look at. The major advantage of using it over other CMS platforms is that it's a very mature platform with a pretty big community around it (Snowcovered for example). For most tasks, it's either already built in or there's already somebody out there that has built a module to do it. Its architecture is already built to support caching and a farm configuration for high-availability applications, which would eliminate a major headache if you're looking at a high volume of requests.

不过，DotNetNuke 可能令人失望的地方是您需要在模块中执行多步骤流程.对于任何 CMS 来说，这可能都是正确的，但是您会觉得自己正在跳过障碍，试图获得多个独立的模块以提供紧密"的用户体验.我真的没有一个具体的例子 - 这只是你从一切都在自己的容器"中的体验中获得的感觉.另一件事是开箱即用，它只是没有 Web 2.0 外观.您可以自定义皮肤和样式表来做任何您想做的事情，但出于某种原因，这对于整个 DNN 阵营来说并不是一个重要的优先事项，就像对 Drupal 和其他人一样.

The place where DotNetNuke could disappoint, though, is when you need to do multi-step processes in your modules. This is probably true for any CMS, but you'll feel like you're jumping through hoops to try to get multiple, separate modules to give a "tight" user experience. I don't really have a concrete example for this - it's just the feeling you get from the experience where everything is in its own "container". The other thing is that out of the box, it just doesn't have a Web 2.0 look to it. You can customize skins and stylesheets to do just about whatever you want, but for some reason this just hasn't been a big priority for the DNN camp as a whole, as much as it has for Drupal and others.

所以我想如果我必须做一个总结，我会说如果你正在寻找一种快速的方法来建立一个可定制的 CMS，并且你对 CMS 平台的一般限制感到满意，那么去它.但是，如果您的 UI 对您来说是最重要的，并且您愿意花费大量精力使其完全符合您的要求，那么请使用 ASP.NET 母版页等创建您自己的应用程序.

So I guess if I had to make a summary, I'd say if you are looking for a quick way to get a customizable CMS up, and you're comfortable with the limitations of CMS platforms in general, then go for it. However, if your UI is the most important thing to you and you're willing to spend a LOT of effort to make it exactly what you want, then create your own application using ASP.NET master pages and the like.

这篇关于我们应该在 DotNetNuke 平台上构建我们的下一代 Web 应用程序吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！