序列化程序集。需要它或不？ [英] Serialization Assembly. Is it needed or not?

问题描述

我有一个.NET 2.0的C＃的ClickOnce应用程序，它通过Web服务连接到其数据。我已经告诉潜在加快应用程序的方法是预先生成序列化程序集。我有这方面的几个问题。

1. 默认设置是否生成序列组装汽车。什么标准VS2005使用来决定是否生成序列化程序集或没有？现在看来似乎在调试配置不会产生，但它下释放配置的做法，但我不能告诉肯定，并不能在任何地方的信息。




2. 是否序列化程序实际上提高了应用程序的启动？具体是什么，是否提高？我是不是真的需要一个序列化程序集？

解决方案

这实在是问要我预先生成序列化组件并将其包括在已部署的项目或我将退到动态生成组件的默认？一般不会伤害太大先打法律约束明智了。凡能起到的是，序列化程序集在％SYSTEMROOT％\TEMP 生成。其中，在一些情况下，该过程不能访问，导致在大多数情况下是致命的例外。

I have a .net 2.0 c# ClickOnce app and it connects to its data via Web Services. I've been told that one way to potentially speed up the application is to generate a serialization assembly beforehand. I have several questions on this front.

1. The default setting to whether to generate a serialization assembly is Auto. What criteria does VS2005 use to decide whether to generate a serialization assembly or not? It seems like it does not generate under Debug configuration, but it does under Release configuration, but I can't tell for sure and can't the information anywhere.

2. Does serialization assembly actually improve the startup of the application? Specifically what does it improve? Do I actually need a serialization assembly?

解决方案

It is really asking "Shall I pre-generate the serialization assemblies and include it in the deployed project or shall I fall back on the default of generating the assemblies on the fly?" Generally that won't hurt too much after the first hit perf-wise. Where it can play in is that the serialization assemblies are generated in %SYSTEMROOT%\TEMP. Which, in some cases, the process can't access, leading to fatal exceptions in most cases.

这篇关于序列化程序集。需要它或不？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！