如何防止 VSeWSS 1.3 将程序集添加到解决方案清单
我最近将我的 SharePoint 开发计算机升级到 VSeWSS 1.3，并注意到我以前认为不存在的行为。我有两个使用多个常见程序集的自定义 Web 部件，并且两者都位于同一站点中。我正在尝试创建第三个“通用”Web 部件，将这些文件复制到 Bin 文件夹并向 web.config 添加安全控制条目，以便我可以根据需要删除其中一个 Web 部件解决方案，而不会损坏另一个 Web 部件解决方案。
对于早期版本的 VSeWSS，我认为它仅在清单中包含程序集（如果您将它们包含在给定的 Visual Studio 项目中）。我已从两个 Web 部件项目中删除了通用程序集，但它们的条目最终仍出现在其解决方案清单中。显然，扩展程序正在查看 Web 部件的引用并遵循该引用，即使文件位于另一个目录中也是如此。
有没有办法告诉扩展不要将程序集条目添加到清单中，即使它们在项目中被引用？或者是否有更好的方法将公共代码与使用它的 Web 部件分开？
I recently upgraded my SharePoint development machine to VSeWSS 1.3 and have noticed a behavior that I didn't think existed before. I have two custom web parts that use several common assemblies, and both will live in the same site. I'm trying to create a third 'common' web part that copies these files to the Bin folder and adds safe control entries to web.config so I can remove one of the web part solutions, if needed, without crippling the other one.
With the prior version of VSeWSS I thought it only included assemblies in the manifest if you included them in the given Visual Studio project. I've removed the common assemblies from the two web part projects, but entries for them still end up in their solution manifests. Obviously the extensions are looking at the references for the web part and going by that, even if the file are in another directory alltogether.
Is there any way to tell the extensions to not add assembly entries to the manifest even if they are referenced in the project? Or is there a better way to separate the common code from the web parts that use it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的，您可以阻止 VSeWSS 部署程序集。只需在 VS 项目中引用的程序集列表中选择程序集并查看其属性即可。在那里您可以找到选项“LocalCopy”，您已将其设置为 false 以防止部署程序集。
Yes you could prevent VSeWSS from deploying assemblies. Just select the assembly in the list of referenced assemblies in you VS project and look at its properties. There you can find the option "LocalCopy", which you have set to false to prevent the assembly from being deployed.