我们应该建立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?
任何你会警惕或建议？
任何意见将是AP preciated，谢谢...
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平台的主要优势在于它是一个非常成熟的平台，它周围的pretty大社区（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屋！
