.net.is版本中的程序集适用于私有程序集 [英] assemblies in .net.is versioning applicable to private assemblies

问题描述

元数据和清单之间的区别是什么，因为两者都存储相同的信息.请
提供解决方案.

what is the difference between metadata and manifest as both stores the same information.please
provide the solution.

推荐答案

否.应该由单个应用程序使用.

您可以对其进行版本控制，但这样做的意义在于，因为您不会将其部署到GAC.

No. It is supposed to be used by a single application.

You can version it but what''s the point since you are not going to deploy it to GAC.

是的，它适用.程序集版本与某些其他程序集私有无关.程序集的版本独立于其他程序集的版本，并且它们之间的引用实际上在运行时使用版本信息，因此，与非私有程序集的情况一样，您应该相应地更新整个解决方案. >
我不知道为什么不保持所有这些简单.在我所有的项目中，我始终保持解决方案中所有程序集的版本相同，并使用为此目的开发的特殊MSBuild任务对其进行检查.另外，在解决方案的结构中，我尝试按项目使用引用(添加程序集时使用Visual Studio选项卡项目")；它使应该在更新版本时自动保持解决方案完整性.

—SA

Yes, it is applicable. Assembly version has nothing to do with the fact of being private to some other assemblies; the versions of assemblies are independent from versions of other assemblies, and the references between them actually use the version information during run-time, so you should update the whole solution accordingly, exactly as in the case of non-private assemblies.

I don''t know why not keeping it all pretty simple. In all my projects I always kept versions of all the assemblies in the solution identical and checked it up using special MSBuild tasks I developed for this purpose. Also, in the structure of the solution I try to use reference by Project (using Visual Studio tab "Projects" when adding an assembly); it makes keeping solution integrity automatic when version should be updated.

—SA

这篇关于.net.is版本中的程序集适用于私有程序集的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！