合并 Sharepoint WSP 解决方案文件
我有多个项目/wsp 解决方案用于不同的 Sharepoint Web 部件和事件接收器。这对于开发来说很好，但是我想将生成的 .wsp 文件合并为一个文件以进行生产部署。 有办法这样做吗？我只使用 vsewss 1.2。
I have multiple projects/wsp solutions for my different Sharepoint webparts and event receivers. This is fine for development, however I would like to merge the resulting .wsp files into a single one for production deployment.
Is there a way to do so? I am using vsewss 1.2 only.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
这将是痛苦的，但要真正正确地为生产推送做到这一点，您应该放弃 vsewss 1.2，在 Visual Studio 内重新组织项目并使用 WSPBuilder。
WSPBuilder 很棒，因为它不需要创建清单、ddf 和编译 CAB 等大量手动工作。
This is going to be painful, but to really do this correctly for production pushes you should drop vsewss 1.2, re-organize your projects inside of Visual Studio and use WSPBuilder.
WSPBuilder is great because it takes a lot of the manual work out of creating manifest, ddf and compiling the CAB.
您将必须自己完成 vsewss 在后台所做的大量工作。 MSDN 上有一篇关于创建 WSP 基础知识的文章在中创建解决方案包Windows SharePoint Services 3.0
WSP 是一个包含manifest.xml 和文件结构的cab 文件，重要的是您将文件放置在WSP 中的正确位置，以便将它们部署到SharePoint 中的正确位置。
我同意JD的观点
这将是重组代码和程序集结构的好时机，以便最大限度地减少需要部署的程序集数量。
如果您有任何 Web 部件，请务必检查功能 xml 文件是否全部正确，因为 vsewss 在生成其 WSP 文件之前准备并进行文本替换。
它通常在需要完整程序集名称的文件中存储 guid。
如果您要进行大量 SharePoint 开发工作，那么可能值得花一些时间来了解 manafest.xml 和其余 WSP 包的工作原理。
You are going to have to do a lot of the work that vsewss is doing in the background your self. there is a artical on MSDN about the basics on creating a WSP Creating a Solution Package in Windows SharePoint Services 3.0
A WSP is a cab file that contains a manifest.xml and a file structure, it is imortant that you place files in the right location in the WSP so they are deployed to the right location in SharePoint.
I agree with JD
This would be a good time to restructure you code and assembly structure so as to minimise the number of assemblies you need to deploy.
If you have any Web Parts be sure to check that the Feature xml files are all corect as vsewss preparses and does text replacment befor generating its WSP files.
It commanly stores a guid in the file where a full assembly name is requierd.
If you are going to be doing a lot of SharePoint dev work it is probly worth spending a bit of time learning how the manafest.xml and rest of the WSP packages work.
我还没有看到一个工具可以做到这一点，但创建它应该不难：
具有奇怪扩展名的 cab 文件）
I haven't seen a tool which does this, but it shouldn't be hard to create:
cab files with an odd extension)
不将所有代码放在一个 WSP 中是有一个优点的。您可以进行部分部署，并且不必将所有代码放在一个巨大的 Visual Studio 解决方案中。
为什么不在 1 个脚本文件中编写所有 WSP 部署的脚本？这似乎是一个比摆弄 WSP 本身更透明的解决方案。
There is an advantage to not having all your code in a single WSP.. you can do partial deployments and you don't have all your code in a single gigantic Visual Studio Solution.
Why don't you script all WSP deployments in 1 script file? It seems a far more transparent solution than fiddling with the WSP itself.