Hello,
I was having some performance problems using xml serialization, so I used sgen to generate an XmlSerializers.dll file.
I then added a reference to myAssembly.XmlSerializers.dll to the vbproj file that's doing xml serialization and to my http://localhost.
However, when I run my website, I still see stuff like:
'aspnet_wp.exe' (Managed (v2.0.50727)): Loaded 'jrenx0rj'
'aspnet_wp.exe' (Managed (v2.0.50727)): Loaded 'hub0a9va'
in my output window. I also see these files still being generated in the temp folder via procmon. So despite it has the XMLSerializers pre-built, it still seems to be building them on the fly.
Is there something else that I need to do?
Any idea why IIS apparently isn't using myAssembly.XmlSerializers.dll?
Could it have something to do with the fact that I'm debugging my website?
Thanks,
Eric
I was having some performance problems using xml serialization, so I used sgen to generate an XmlSerializers.dll file.
I then added a reference to myAssembly.XmlSerializers.dll to the vbproj file that's doing xml serialization and to my http://localhost.
However, when I run my website, I still see stuff like:
'aspnet_wp.exe' (Managed (v2.0.50727)): Loaded 'jrenx0rj'
'aspnet_wp.exe' (Managed (v2.0.50727)): Loaded 'hub0a9va'
in my output window. I also see these files still being generated in the temp folder via procmon. So despite it has the XMLSerializers pre-built, it still seems to be building them on the fly.
Is there something else that I need to do?
Any idea why IIS apparently isn't using myAssembly.XmlSerializers.dll?
Could it have something to do with the fact that I'm debugging my website?
Thanks,
Eric
