vsewss | 易学教程

Deploying SharePoint Solution using VSeWSS

阅读更多关于 Deploying SharePoint Solution using VSeWSS

问题 I have a development WSS 3.0 site that I wanted to move to a Production server. I am using VSeWSS 1.2 to do my deployment. I generated the SharePoint solution of the site with SharePoint Solution Generator 2008. When deploying it locally it works fine, but when I tried to deploy it to the remote Production server it would not deploy. I then had to install VS and the VSeWSS on the Production server and deploy from there because of time constraints. I have seen references where the generated

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

Building a WSP File on the Build Machine

阅读更多关于 Building a WSP File on the Build Machine

问题 On my development machine I installed VSeWSS 1.3 and configured the local IIS 6 so that I can build my SharePoint project and deploy the generated WSP file to the local machine. The WSP file is generated by the Packaging step, which I can successfully install on other machines. Now I have to migrate my project to our build machine which currently does not have SharePoint installed and is not configured for VSeWSS (no VSeWSS web service endpoint). Is there a way to automate the building of the

Building a WSP File on the Build Machine

阅读更多关于 Building a WSP File on the Build Machine

On my development machine I installed VSeWSS 1.3 and configured the local IIS 6 so that I can build my SharePoint project and deploy the generated WSP file to the local machine. The WSP file is generated by the Packaging step, which I can successfully install on other machines. Now I have to migrate my project to our build machine which currently does not have SharePoint installed and is not configured for VSeWSS (no VSeWSS web service endpoint). Is there a way to automate the building of the WSP file without the need to configure IIS on the build machine for use with SharePoint and VSeWSS?