The simple constructors of XMLSerializer class caches the typed serializer
once it is generated.

(Probably as you know, other XMLSerializer constructors will result in a
memory leak because they will generate the assembly each time instead of
using the cached one)

a) When an XMLSerializer is used from ASP.NET, where exactly the generated
typed serializer is getting cached? What is the probability/crieteria for the
object in the cache may get distroyed/invalidated?

b) Can we assume that once the XMLSerializer is initialized with the
constructor XMLSerializer (sometype), all further XMLSerializer constructor
initializations for sometype, will use the cached serializer?

c) Also, we found that SGen is crashing when classes with same name exists
under different namespaces in the source assembly. Any fixes?



--------------------------------------------------------------------------------
Anoop - Spiritual Programming!! - Articles on design patterns & .NET -
http://amazedsaint.blogspot.com