理解程序集和来自不同程序集的资源存在问题
这本书是《WPF Unleashed》，它告诉我们也可以使用来自不同程序集的二进制资源，但它没有解释程序集的概念以及将资源打包在不同程序集中的需要。所以我把问题放在这里。
我尝试用 google 搜索它，但找不到答案让我能够理解 WPF 中的程序集，以及如何使用 Visual Studio 2010 创建仅包含资源的程序集？
其次，将资源打包在不同的组件中的优势是什么，除了可以更新它们而无需运送全新的产品组件。
The book is WPF Unleashed, and it tells that binary resources from a different assembly can be used as well, but what it doesn't explain is the concept of assembly and the need to pack resources in a different assembly. So i put the question here.
I tried to google it, but couldn't find the answer that allows me to comprehend what is an assembly in WPF, and how to create an assembly that just consist of resources using Visual Studio 2010?
And second, what is the advantage of packing resources in a different assembly except that they can be updated without shipping a brand new assembly of the product.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
WPF 程序集在结构和使用方面与任何其他 .NET 程序集没有什么不同。它们是应用程序（Web、Windows、服务等）部署的基本单元，并包含用于执行 .NET 应用程序的资源。
我会看一下 MSDN 文章< /a> 在程序集上——这非常简单。
关于你的第二个问题，我在这里重复一下我的评论。您已经回答了有关将资源打包在单独的程序集中的问题 - 您可以重新部署该单独的程序集，而无需重新部署或重建原始产品。你必须喜欢那样。能够将一个程序集放入您的 bin 目录中，该程序集包含一堆您想要在站点上显示的自定义小部件，并让您的站点自动探测 bin 目录并获取满足其条件的所有资源，这真是太棒了。我最终不必接触我的主应用程序——只需为我的新资源创建一个新项目，将其编译为单独的程序集（在本例中为 DLL），然后将其放入“bin”中，瞧！惊人的。
希望这有帮助。
WPF assemblies are no different than any other .NET assembly in terms of structure and use. They are the fundamental unit of deployment of an application (web, windows, service, etc) and contain resources for the execution of a .NET application.
I'd take a look at the MSDN article on assemblies -- it's pretty straightforward.
As for your second question, I'll repeat my comment here. You already answered your question about packing resources in a separate assembly -- you can redeploy that separate assembly without having to redeploy or rebuild your original product. You gotta like that. Being able to drop in to your bin directory an assembly that has, say, a bunch of custom widgets that you want to display on your site and having your site automatically probe the bin directory and grab all of the resources that meet its criteria is wonderful. I don't end up having to touch my main app -- just create a new project for my new resources, compile it to a separate assembly (DLL in this case) and just drop it in 'bin' and voila! Awesome.
Hope this helps.
这是一个起点：
.NET 程序集上的 wiki
程序集类似于 C++ DLL，但是它还有一些其他特征，例如描述可供使用的类的元数据。
将资源打包在不同的程序集中的一个优点是它提供了单一参考点 - 如果您需要在使用多个程序集的应用程序（或许多应用程序）中重用资源，那么这是一个很好的策略。如果这些资源需要本地化，这尤其有用。
WPF 不定义程序集，该概念是在 .NET Framework 中定义的。
Here's a starting point:
wiki on .NET Assemblies
An Assembly is similar to a C++ DLL, but it has some other characteristics, such as metadata which describes the classes that are available for use.
One advantage of packing resources in a different assembly is that it gives a single point of reference - if you need to reuse resources across an application (or many applications) that use multiple assemblies, then this is a good strategy to adopt. This is particularly useful if those resources need to be localized.
WPF does not define assemblies, the concept is defined across the .NET Framework.