有什么理由不强烈命名大会？ [英] Any reason NOT to strong-name an assembly?
问题描述
任何人都可以想到为什么第三方供应商编写.NET组件
会不会强烈命名他们的程序集？添加一个强名称
给装配有什么害处 - 我认为没什么。
强化命名程序集应该让最终用户受益case他/她
想要在另一个强名命的程序集中引用程序集，或者将它添加到GAC的
。如果您是第三方供应商，您是否会为您的
组装强名？
我们非常感谢您的反馈。
谢谢
TJ
Can anyone think of a reason why a 3rd party vendor writing .NET components
would NOT strong name their assemblies? What harm does adding a strong-name
to assembly present - I would think none whatsoever.
Strong-naming the assembly should benefit the end user just in case he/she
wants to reference the assembly in another strong-named assembly or add it
to the GAC. If you were a third-party vendor, would you strong-name your
assemblies??
Any feedback is appreciated.
Thanks
TJ
推荐答案
嗯，有一个问题是，如果他们使用auto版本控制，所有使用
程序集的项目都需要在每次供应商的dll改为b $ b时重新编译。当然解决方案是修复版本 - 无论如何都应该发生
。
但我同意你的看法。如果我从供应商那里购买一个组件，我会希望它是强大的名字，否则我会质疑供应商对他们正在做什么的了解b
如果他们没有这样做他们的专业精神
这个。
" Tony Jones" <到******* @ junk.hotmail.com>在留言中写道
新闻：％2 **************** @ tk2msftngp13.phx.gbl ...
Well, one issue is that if they use auto versioning, all projects using the
assembly would need to be recompiled every time the vendor''s dll was
changed. Of course a solution would be to fix the version - which should
probably happen anyway.
But I agree with you. If I am buying a component from a vendor, I would
expect it to be strong named, otherwise I would question the vendor''s
knowledge of what they are doing and their professionalism if they didn''t do
this.
"Tony Jones" <to*******@junk.hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
任何人都可以想一想为什么编写.NET
组件的第三方供应商不会强烈命名他们的程序集？在装配中添加一个强名称会有什么害处 - 我绝不会想到任何一个。
强大命名程序集应该对最终用户有利，以防万一他/她
想要在另一个强名命的程序集中引用程序集或将其添加到GAC。如果您是第三方供应商，您是否会为您的
组件命名？
任何反馈都表示赞赏。
谢谢
TJ
Can anyone think of a reason why a 3rd party vendor writing .NET
components
would NOT strong name their assemblies? What harm does adding a
strong-name
to assembly present - I would think none whatsoever.
Strong-naming the assembly should benefit the end user just in case he/she
wants to reference the assembly in another strong-named assembly or add it
to the GAC. If you were a third-party vendor, would you strong-name your
assemblies??
Any feedback is appreciated.
Thanks
TJ
你好，
Tony Jones写道：
Hi,
Tony Jones wrote:
如果你是第三方供应商，
你会强烈命名你的程序集吗？
If you were a third-party vendor,
would you strong-name your assemblies??
是的，当然。没有充分理由不这样做。
-
Patrick Philippot - 微软MVP
MainSoft咨询服务
www.mainsoft.fr
Tony Jones< to ******* @ junk.hotmail.com>写道：
Tony Jones <to*******@junk.hotmail.com> wrote:
任何人都可以想到为什么编写.NET组件的第三方供应商不会强烈命名他们的程序集？在装配中添加一个强名称会有什么害处 - 我不会想到任何一个。
Can anyone think of a reason why a 3rd party vendor writing .NET components
would NOT strong name their assemblies? What harm does adding a strong-name
to assembly present - I would think none whatsoever.
它强制任何引用你的程序集的东西也强烈
命名，不是吗？对于那些想要使用
组件而又不需要强名的人来说，这会增加复杂性。
-
Jon Skeet - < sk *** @ pobox.com>
http://www.pobox.com/~skeet
如果回复小组，请不要给我发邮件
It forces anything that references your assembly to also be strongly
named, doesn''t it? That adds complications for people who want to use
the assemblies but don''t have any need for strong names.
--
Jon Skeet - <sk***@pobox.com>
http://www.pobox.com/~skeet
If replying to the group, please do not mail me too
这篇关于有什么理由不强烈命名大会？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
