如何在DotNetNuke 5.6.2中构建专业模块？
如何构建稍后可在其他 DNN 网站中使用的自定义模块。
- “标准”：模块只能在一个 DNN 门户中安装一次
- “专业”：模块可以在多个门户中安装
- “企业”：模块可以在多个门户中安装多次
- “试用版”：模块只能在 1 个门户中安装访问权限有限的门户。
模块开发中是否可以满足这个需求？
How can I build custom module that can later be useful in other DNN websites.
- "standard" : module can be installed once only in one DNN portal
- "professional" : module can be installed in multiple portals
- "Enterprise" : module can be installed multiple times in multiple portals
- "Trial release" : module can be installed only in 1 portal with limited access.
Is this possible to fulfill this requirement in module development?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
截至目前，还没有 API 可供您自动执行此操作，但您完全能够添加自己的许可流程来实现此目的。
As of this point in time there is no API for you to do this automatically, but you are more than able to add your own licensing process to make this happen.
这里有两个概念需要澄清。
安装 - 获取模块并使其可在 DNN 站点上使用。通常，这是通过 .zip 包和模块安装向导完成的，但还有其他方法可以使模块可供站点使用。模块可以安装在管理员（门户）级别，这意味着它只能在该特定门户中使用，也可以安装在主机级别，这意味着它可以在任何门户上使用。
模块实例 - 安装模块后，可以将其一次或多次添加到一页或多页。每次添加模块时，都会创建一个附加模块实例。可以在多个位置共享单个实例。
“普通”模块不受限制。它可以安装在管理员或主机级别，并且可以在整个门户中创建无限数量的实例。框架中没有任何内容可以限制模块的安装或实例。每个模块开发人员都必须提供自己的商业许可机制。
There are two concepts here that should be clarified.
Installation - taking a module and making it available to be used on a DNN site. Typically this is done via a .zip package and the module installation wizard, but there are other ways to make a module available to site. A module can be installed at the Admin (portal) level which means it can only be used in that specific portal, or it can be installed at the Host level which means it can be used on any portal.
Module Instance - once a module is installed it can be added one or more times to one or more pages. Each time a modules is added, an additional module instance is created. It is possible to share a single instance in multiple locations.
A "normal" module is unrestricted. It may be installed at the Admin or Host level and an infinite number of instances may be created throughout the portal(s). There is nothing in the framework to restrict the installation or instances of a module. Each module developer is left to provider their own commercial licensing mechanism.
这听起来更像是一个许可问题，而不是功能问题。您可以将其中每一个视为模块的不同版本。如果您将该模块与 DNN 许可解决方案（例如 Licence Master）集成，您可以控制在每个不同版本中“打开”应用程序的哪些功能。
This sounds more a licensing issue rather than one of functionality. You can consider each of these as different editions of your module. If you integrate the module with a DNN licensing solution such as Licence Master, you can control which features of the application are "switched on" in each of the different editions.