如何部署在 Visual Studio 2008 中创建的 SharePoint 工作流？
我在 Visual studio 2008 中创建了一些共享点工作流程，它们在我的计算机上完全按照要求工作。我通过将它们部署到共享点服务器上的几个不同的 Web 应用程序进行了测试。作为客户端的包，我为三个工作流程创建了 WSP，并将它们与 install.bat 和 uninstall.bat 一起发送到客户端，以从共享点站点设置或卸载功能。然而，最后出现了一个奇怪的问题，即无法通过 install.bat 文件中的 stsadm 命令激活这些功能。这些功能也未在“网站集功能”屏幕中列出，因此无法从那里激活它们。此外，在操作页面的解决方案管理中；这些解决方案已在全球部署。由于某些 IP 限制，我无法访问服务器，因此我无法解决该问题。我想问一下，除了使用wsp来部署工作流程之外；我还可以使用哪些其他方法来部署工作流程。我的意思是我应该向客户发送哪些内容以及他应该遵循哪些部署说明？ （不需要使用wsp的方法）
I have created some sharepoint workflows in Visual studio 2008 and they work exactly as required on my machine. I have tested by deploying them to several different web applications on the sharepoint server. As a package to the client, I created WSP's for the three workflows and sent them to the client along with an install.bat and an uninstall.bat to setup or uninstall the features from the sharepoint site. However, there is a strange problem occuring at their end which is that the features cannot be activated from the stsadm commands in the install.bat file. The features are also not listed in the Site Collection Features screen so they cannot be activated from there. Also, in the Solution Management from the Operations page; the solutions are globally deployed. I am unable to access the server due to some IP restrictions so I cannot play around with the problem. I want to ask, other than using the wsp's to deploy the workflows; what other ways can i use to deploy a workflow. I mean what stuff should I send to my client and what deployment instructions he should follow? (a method that does not require using wsp's)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
使用 WSP 文件是将代码部署到 SharePoint 的唯一正确方法。虽然您可以手动复制相同的文件，但这既更复杂，也不太可能解决问题。
由于激活功能不起作用，因此安装步骤可能出现问题。检查 12 个配置单元中是否存在预期的功能文件夹，并且 feature.xml 文件中的 id 是否与您尝试激活的功能 id 匹配 - VSeWSS 经常生成具有相同名称但不同 id 的功能，这将导致各种问题如果存在早期版本，则会出现问题。您还需要检查这些功能是否未被隐藏，如果它们旨在以编程方式激活，则这是可能的。
Using WSP files is the only correct way to deploy code to SharePoint. While you could copy the same files manually, that's both more complicated and unlikely to fix the issue.
Since activating the features doesn't work, there is probably something going wrong with the install step. Check that the expected feature folders exist in the 12 hive, and that the ids in the feature.xml files there match the feature ids you are trying to activate - VSeWSS often generates features with the same name but different ids, which will cause all sorts of problems if an earlier version is present. You'll also want to check that the features aren't hidden, which is possible if they were intended to be activated programmatically.