SharePoint Web 部件开发环境
我知道关于这个主题的问题和文章太多了，到目前为止我已经在互联网上搜索了好几个小时，但我仍然找不到我的问题的正确答案。我的公司分配给我调查 SharePoint Web 部件的开发环境的任务。钱不是问题，但一定要有正确的方法。
这是我的理想计划：在开发人员桌面上安装VS2005/2008（已经安装）、VS2005/2008 SharePoint 扩展和WSPBuilder。它还安装了虚拟机，VM 运行 Windows Server 2003/2008。 WSS3.0 和 SQL Express 2005/2008 也将安装在 VM 上。
开发人员桌面是一个Web 部件开发环境。开发人员使用VS开发SharePoint Web Part，然后运行WSPBuilder，它将Web Part部署到VM上的SharePoint测试环境中。所以VM只是一个SharePoint测试环境。 这看起来是个好主意，然而，它行不通。为什么？因为VS扩展无法安装在开发者桌面上，因为它没有安装WSS3.0！
我绝对不想在VM上安装VS，因为我们的开发人员桌面已经安装了VS，我们不需要为1个开发人员拥有2个VS许可证。 您知道设置 SharePoint Web 部件开发环境的最佳方法是什么吗？
先感谢您。
I know there are so many questions and articles on this topic and I have searched hours and hours on the Internet so far, but I still couldn’t find the right answer for my question. I was assigned the task to investigate the development environment for SharePoint web parts by my company. The money is not an issue but it must be the proper way to do it.
Here is my ideal plan: at developer desktop, install VS2005/2008 (it is already installed), VS2005/2008 Extension for SharePoint and WSPBuilder. It is also installed a Virtual Machine and the VM runs windows server 2003/2008. WSS3.0 and SQL Express 2005/2008 will be also installed on VM.
Developer’s desktop is a web parts development environment. Developers use VS to develop the SharePoint web parts and then run the WSPBuilder, it will deploy the web parts into the SharePoint testing environment on VM. So the VM is just a SharePoint testing environment.
It looks like a good idea, however, it doesn’t work. Why? Because VS extension can't be installed on developer’s desktop as it doesn’t have WSS3.0 installed!
I definitely don’t want to install the VS on the VM, because our developer desktop has installed VS and we don’t need to have 2 VS licences for 1 developer.
Any idea what is the best way to set up the development environment for SharePoint web parts?
Thank you in advance.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
适合您的替代方案可能有效也可能无效，具体取决于您的优先事项。
将 Visual Studio 2010 和SharePoint 2010 Foundation 安装到您的开发服务器。
从 SharePoint 2007 服务器获取 Microsoft.SharePoint.dll 的副本。
使用 VS2010 的工具开发 Web 部件，但手动更改对 2007 dll 的引用（另请参阅“使用 Visual Studio 2010 可视化 Web 部件项目构建 SharePoint 2007 Web 部件 ") 因此您将输出 2007 兼容的 Web 部件。
当您将 2007 Web 部件部署到本地 2010 服务器时，它将正常工作 （因为它向后兼容）
当您将 2007 Web 部件部署到测试/质量保证/生产服务器时，它也将起作用。
优势
VS 版本和共享点
工具，让您可以一键部署，
自动创建 WSP 包
等等。我并不是反对 WSP Builder 等（它们很棒），但我把钱花在了未来的 vs2010 共享点扩展上。
公司移至 2010 年。
编辑- 要将 Web 部件部署到其他服务器，您需要创建一个 .wsp 包，然后通过 STSSADM 或其他工具（SharePoint 解决方案安装程序或其他管理工具）进行部署。
An alternative for you which may or may not work depending on your priorities.
Install Visual Studio 2010 and SharePoint 2010 Foundation to your development server.
Grab a copy of Microsoft.SharePoint.dll from a SharePoint 2007 server.
Use VS2010's tools to develop a web part but manually change the reference to the 2007 dll's (+ also see "Build a SharePoint 2007 Web Part with a Visual Studio 2010 Visual Web Part Project") so you are outputing a 2007 compatible web part.
When you delploy your 2007 web part to your local 2010 server it will just work (as its backwardly compatible)
When you deploy your 2007 web part to your test/qa/production servers it will work too.
Advantages
version of VS and the sharepoint
tooling so you get one click deploy,
automatic creation of WSP packages
etc. Nothing against WSP Builder etc (they are great) but my moneys on vs2010 sharepoint extensions for the future.
company moves to 2010.
Edit - to deploy web parts to other servers you create a .wsp package and then deploy via STSSADM or another tool (SharePoint solution installer or other admin tools).
我没有使用过 VSSWSS 或 WSPBuilder。我一直使用 SharePoint 2007 的 STSDEV。而且我一直使用 Windows XP 来执行此操作。我不知道 VSSWSS 和 WSPBuilder 的行为是否相同，但是，正如 Ryan 所说，我将所需的任何 SharePoint DLL 从 SharePoint 2007 服务器复制到我的 Visual Studio 解决方案中的解决方案文件夹中。然后，我选择在项目中添加引用并浏览到 DLL。
四年来，我使用这个方法从来没有遇到过任何问题。该解决方案包构建得很好，可以在任何 SharePoint 服务器上运行。我失去了调试选项，但我宁愿留在我的机器上，也不愿进入虚拟机或远程桌面。
I haven't used VSSWSS or WSPBuilder. I've always used STSDEV for SharePoint 2007. And I've always used Windows XP to do it. I don't know if VSSWSS and WSPBuilder act the same, but, as Ryan was saying, I copy whatever SharePoint DLLs I need from a SharePoint 2007 server into a Solution Folder in my Visual Studio solution. I then select Add Reference in my project and browse to the DLL.
In four years, I've never had any problems with this method. The solution packages build just fine and work on any SharePoint server. I lose the option to debug, but I'd rather stay on my machine than go into a VM or Remote Desktop.
除非您的开发环境至少包含 WSS 的安装，否则您将无法针对 SharePoint (WSS 3.0) 进行开发。一般来说，开发是在Windows Server 2003虚拟机上完成的（Visual Studio直接安装在该机器上）。但是，SharePoint 可以安装在 Windows Vista 和 Windows 7 计算机上，因此您的开发计算机可能能够托管 SharePoint 本身，但在 VM 上执行此操作要容易得多。
我的 SharePoint 开发 VM 安装了以下内容：
显然您可以使用 WSPBuilder，但我更喜欢 VSSWSS 1.3 ，但这是开发人员的偏好。
我相信（应与 Microsoft 验证）当同一开发人员使用时，Visual Studio 的许可可以扩展到虚拟机（取决于您的协议）。
You won't be able to develop for SharePoint (WSS 3.0) unless your development environment includes an installation of at least WSS. In general, development is done on a Windows Server 2003 Virtual Machine (Visual Studio is installed directly on this machine). However, SharePoint can be installed on Windows Vista and Windows 7 machines, so your development machine may be able to host SharePoint itself, but it is far easier to do this on a VM.
My SharePoint development VM has the following installed:
Obviously you can use WSPBuilder instead, but I much prefer VSSWSS 1.3, but that is developer preference.
I believe (should be verified with Microsoft) that the licensing for Visual Studio can be extended to Virtual Machines when used by the same developer (depending on your agreement).