The temporary files are not created by developers - they're automatically created by the .net framework if needed (module developers don't have access to the temp folder - in fact if you're running under medium trust no developer code can access files outside the web app folder itself). Typically the two things that generate these assemblies are XSD validation and classes marked with the xmlserialzation attribute. As I mentioned, the framework will generate these but will also delete them when it's finished with them - the time they exist is usually measured in milliseconds. If they're staying longer than that then you have a problem e.g. perhaps the permissions on the folder are incorrect (if the permissions allow for creation and read of files, but not delete you would see this).

Cathal

Also, if any applications are using XSLT, combined with .NET code embedded in the XSLT file....that causes dll's to be written to the windows temp dir.  When the XSLT is parsed, when it finds .NET code in there, it compiles it into a .dll and puts it in the windows temp dir...and it doesn't cache it, everytime you do a transformation, it creates a new .dll.  We had tens of thousands of them, growing at an alarming rate...evenutally the server ran out of space on the C drive.  It had nothing to do with DotNetNuke in this case (DNN wasn't even installed on this server).

Dan