wsp | 易学教程

TFS Build 2010 - Custom Binary Location and SharePoint WSP

阅读更多关于 TFS Build 2010 - Custom Binary Location and SharePoint WSP

问题 I'm building a solution using TFS Build 2010. This solution has multiple projects and one of the projects is SharePoint. I want TFS Build to put binaries for each project in its own folder (i.e. customized binary folder). So I followed the instructions from MSDN and it works. Now the challenge is that I'm not able to generate a WSP file with the customized binary folder (note that I'm able to generate WSP without the customized binary folder). I'm getting this error: C:\\..\..\Microsoft

Can't find workflow deployed as WSP solution (when I deploy it from VS it works)

阅读更多关于 Can't find workflow deployed as WSP solution (when I deploy it from VS it works)

问题 I am new to SharePoint, sorry if answer to my question is obvious. I am trying to deploy my very simple workflow as WSP package, it deploys without errors, I activate it, but I can't find my workflow and associate it with list. Could you help me, please, what I do wrong? I do it so: Create empty project Choose trust level as a Farm solution Add State Machine Workflow Choose list Workflow Associate workflow with list Task Create simple workflow Press CTRL-F5 in VS2010, and see that WF appears

TFS 2010 Building Sharepoint 2010 Solution With Custom Outputs

阅读更多关于 TFS 2010 Building Sharepoint 2010 Solution With Custom Outputs

问题 I have a very similar question to this SO post: TFS Build 2010 - Custom Binary Location and SharePoint WSP. There's no marked answer, but the only answer provided seemed to be the path to go. I'm building several solutions and need the solutions and projects to be placed into their own folders. This lead to the build output change to the MSBuild call in the template that I'm using. I've been using this for sometime without any issues. Recently a developer complained that the .wsp files were

Sharepoint WebPart, include additional assembly in wsp package

阅读更多关于 Sharepoint WebPart, include additional assembly in wsp package

问题 I created a utility library for my Sharepoint WebParts. Now when I reference this library from my WebPart project, it compiles fine, but the library is not included in the .wsp package. This means the library assembly is not deployed to the target system, causign the WebPart to fail. Is there any way to fix this? I am using Visual Studio 08 & VseWSS 1.2. 回答1: Brij's answer is partially correct, your VSeWSS version is the problem. This feature only came in version 1.3 (I recommend the March

Sharepoint 2010 register control as safe through wsp

阅读更多关于 Sharepoint 2010 register control as safe through wsp

问题 I created a "Hello World" Sharepoint 2010 solution using VS2010. It contains just a feature, and a webpart containing a label. I registered the webpart as a safe control in the "Properties" window of the webpart, in VS2010. When I deploy my solution to my local server, everything works great! I can add the webpart to a page, and in the web.config file my control is added to the SafeControls list. When I install the same solution on a different server, I can see the webpart in the list of

SharePoint wsp solution: How to Deploy Globally

阅读更多关于 SharePoint wsp solution: How to Deploy Globally

问题 I have created a wsp package and add it to Central Administration > Operations > Solution Management using the addsolution command of stsadm. When I click on the Deploy Solution menu, it transfers me to deploy to the solution page. In this page, in the "Deploy To?" section, it shows me a dropdown list with entries like 'All Content web Applications'. I want to deploy my solution globally so that it is applicable to all new web applications created after the deployment. I have seen WSPs for

Sharepoint 2010 register control as safe through wsp

阅读更多关于 Sharepoint 2010 register control as safe through wsp

I created a "Hello World" Sharepoint 2010 solution using VS2010. It contains just a feature, and a webpart containing a label. I registered the webpart as a safe control in the "Properties" window of the webpart, in VS2010. When I deploy my solution to my local server, everything works great! I can add the webpart to a page, and in the web.config file my control is added to the SafeControls list. When I install the same solution on a different server, I can see the webpart in the list of available webparts, but when I try to add it to the page, it tells me that it's not registered as safe.

SharePoint wsp solution: How to Deploy Globally

阅读更多关于 SharePoint wsp solution: How to Deploy Globally

I have created a wsp package and add it to Central Administration > Operations > Solution Management using the addsolution command of stsadm. When I click on the Deploy Solution menu, it transfers me to deploy to the solution page. In this page, in the "Deploy To?" section, it shows me a dropdown list with entries like 'All Content web Applications'. I want to deploy my solution globally so that it is applicable to all new web applications created after the deployment. I have seen WSPs for which "Deploy To?" section shows only a message like "This solution deploys globally" and no dropdown