商业 SharePoint 产品版本的解决方案/功能
假设您正在为 SharePoint 创建商业产品。该产品将提供社区（免费）和企业（付费）版本。
社区版的代码库是一个带有小增量的子集，所有这些增量都通过 (C#) #define 语句进行处理。实际上，它是一个单一的代码库。构建过程构建两个解决方案（每个解决方案包含两个功能），每个版本一个。
不可能同时在场中安装两个版本。当前的业务模型仅为单服务器 SharePoint 场提供社区/免费版本。这是为了支持个人和开发场景。
该解决方案包括各种功能元素，但目前没有 Web 部件。未来版本中可能会包含一个或多个 Web 部件。从长远来看，任何限制解决方案/功能内容的方法可能都不是最好的主意。
您会在多大程度上跨版本重复使用解决方案和/或功能 ID？为什么？
Assume for a moment that you are creating a commercial product for SharePoint. This product will be offered in both Community (free) and Enterprise (pay) editions.
The code base for the Community edition is a subset with minor deltas all handled through (C#) #define statements. Effectively it's a single code base. The build process builds two solutions (each containing two features), one for each edition.
It should not be possible to install both editions in a farm at one time. The current business model offers the community/free version only for single server SharePoint farms. This is intended to support individuals and development scenarios.
The solutions include a variety of functional elements but currently no web parts. It is possible that one or more web parts may be included in a future release. Any approach that limits solution/feature contents is probably not the best idea in the long run.
To what extent would you reuse solution and/or feaure ids across the editions? Why?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我希望人们能够轻松地从免费升级到完整（如果他们选择这样做）。
想象一下 Web 部件的情况 - 如果您设置了免费 Web 部件的几个版本，然后卸载它并安装完整的 Web 部件，那么大多数人会希望所有现有实例继续工作，但在新的 Web 部件上，
我认为您会需要保持solutionId相同才能正常工作。
您还需要使完整的程序集名称相同（文件版本可以不同）或设置绑定重定向。
哦 - 当然，您的代码中没有重大更改。
I would want people to be able to easily upgrade from free to full if they choose to do so.
Imagine the case of a web part - if you setup a few versions of the free web part, then unintall it and install the full web part then most people will want all existing instances to keep working but on the new web part
I think you would need to keep the solutionId the same for this to work.
You would also need to have the full assembly name the same (the file version can be different) or setup binding redirects.
Oh - and no breaking changes in your code of course.
我将使用相同的 ID 并提供额外的功能来解锁企业功能。
此功能包含解锁企业版所需的额外 dll、Web 部件、许可证密钥等。
我将确保用户在升级后可以继续使用您的产品，而无需更改其自定义设置。
I would use the same id's and provide an extra feature to unlock the enterprise functionality.
This feature contains the extra dlls, web parts, license keys, ... needed to unlock the Enterprise Edition.
I would make sure that the users can continue using your product after the upgrade without having to change their customizations.