加速 VS2010“SharePoint” Web 部件开发的周期时间
我正在开始处理 SharePoint 2010 项目，并使用 Visual Studio 2010 内置 Magical 扩展来执行此操作。然而，重新部署解决方案的周转周期非常长（构建、打包、收回、部署、然后重新启动等）。在此期间唯一的更改是对单个 Web 的更改部分。
过去，我使用过 WSP Builder，并且仅使用 Copy-to-GAC/Copy-to-Hive 功能对开发盒进行小幅更新，该功能的周转时间要短得多 /em> 查看 Web 部件的更改。我想知道是否有类似的（或替代的）方法可以在 VS2010 中获得类似的快速周转？映射文件夹地址是一个不断变化的视图，但现在我最感兴趣的是 Web 部件。
拜托，如果您想说“但您应该始终重新部署”，请仅将其作为建议和其他[有用]建议 - 测试服务器将得到完全重新部署。这只是为了帮助我缩短开发周期时间。
I am starting work on a SharePoint 2010 Project and using the Visual Studio 2010 Built-In Magical Extension to do so. However, the turn-about cycle to re-deploy the solution is terribly long (build, package, retract, deploy, then restart, etc.) The only changes during this time have been to the individual Web Parts.
In the past I have used WSP Builder and for minor updates on the dev box just using the Copy-to-GAC/Copy-to-Hive features which has a much shorter turn-about to see changes to a Web Part. I was wondering if there was a similar (or alternative) method to get a similar quick turn-about in VS2010? The Mapped Folders address say, a changing view, but it's the Web Parts that interest me most now.
Please, if you are going to say "but you should always re-deploy", please do so only as a suggestion with other [useful] advice -- the testing servers get a full re-deploy. This is simply about helping me reduce the development cycle times.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Visual Studio 2010 中的复制到 14/复制到 GAC 功能
Copy to 14 / Copy to GAC functionality in Visual Studio 2010
如果您部署 BIN 目录而不是 GAC，那么您只需在构建后进行复制即可 - 无需重新启动/部署等。
If you deploy the BIN directory rather than the GAC then you can just do a copy on postbuild - no restart/deploy etc needed.