绝对更喜欢直接使用 SharePoint 在 VM 中工作，因为我可以正确调试进程，而且我还有 构建脚本，它将重新部署我的整个解决方案或让我刷新 GAC。
Definitely prefer working in VM with SharePoint directly as I can debug into processes correctly, also I have a build script that will either redeploy my entire solution or let me just refresh the GAC.
对我帮助最大的一个项目是 Visual Studio 中的后期构建事件，您可以通过一些脚本来完成所有的事情，这真是太神奇了。
I do all my development work on one of my VMware images. Since I try to do my SharePoint work in a TDD style I run a lot of tests and then the remote stuff just don't make sense to me.
The single item that have helped me the most is the post build event in visual studio, it is really amazing all the things you can do with a bit of scripting.
Running SharePoint/VS on the same server (either physical or virtual) will get you up and running quickly, but personally I don't think its the way to go.
In addition to what you describe (local VS/SharePoint running in VM's) then a few tips that may make your life easier.
1) Deploy to the bin directory rather than the GAC, then to update all you have to do is copy over your dll/pdb's in a post build batch file - don't think you can do that automatically if they are in the GAC on a remote machine can you?
2) Look at remote debugging - it can be a little bit of a pain to get working first but the effort is worth it! key tip is you need to use the same username/password on both the local and remote machine.
发布评论
评论（3）
绝对更喜欢直接使用 SharePoint 在 VM 中工作，因为我可以正确调试进程，而且我还有 构建脚本，它将重新部署我的整个解决方案或让我刷新 GAC。
Definitely prefer working in VM with SharePoint directly as I can debug into processes correctly, also I have a build script that will either redeploy my entire solution or let me just refresh the GAC.
我的所有开发工作都是在我的一个 VMware 映像上完成的。 由于我尝试以 TDD 方式完成 SharePoint 工作，所以我运行了大量测试，然后远程内容对我来说没有意义。
对我帮助最大的一个项目是 Visual Studio 中的后期构建事件，您可以通过一些脚本来完成所有的事情，这真是太神奇了。
I do all my development work on one of my VMware images. Since I try to do my SharePoint work in a TDD style I run a lot of tests and then the remote stuff just don't make sense to me.
The single item that have helped me the most is the post build event in visual studio, it is really amazing all the things you can do with a bit of scripting.
在同一服务器（物理或虚拟）上运行 SharePoint/VS 将使您快速启动并运行，但我个人认为这不是正确的方法。
除了您所描述的内容（在虚拟机中运行的本地 VS/SharePoint）之外，还有一些可能会让您的生活更轻松的提示。
1）部署到 bin 目录而不是 GAC，然后要更新您所要做的就是将 dll/pdb 复制到构建后批处理文件中 - 如果它们位于 GAC 中，则不要认为您可以自动执行此操作远程机器可以吗？
2) 查看远程调试 - 它可能有点首先开始工作很痛苦，但努力是值得的！ 关键提示是您需要在本地和远程计算机上使用相同的用户名/密码。
此页面相关 -
调试 SharePoint 2007 代码
Running SharePoint/VS on the same server (either physical or virtual) will get you up and running quickly, but personally I don't think its the way to go.
In addition to what you describe (local VS/SharePoint running in VM's) then a few tips that may make your life easier.
1) Deploy to the bin directory rather than the GAC, then to update all you have to do is copy over your dll/pdb's in a post build batch file - don't think you can do that automatically if they are in the GAC on a remote machine can you?
2) Look at remote debugging - it can be a little bit of a pain to get working first but the effort is worth it! key tip is you need to use the same username/password on both the local and remote machine.
This page is related -
Debugging SharePoint 2007 Code