[Mono-bugs] [Bug 78230][Blo] New - Access Denied error related to deleting and accessing of .CS files generated during XmlSerialization object creation from multiple threads/processes on the same machine

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by apasumarthi at alliance-consulting.com.

http://bugzilla.ximian.com/show_bug.cgi?id=78230

--- shadow/78230	2006-04-28 05:43:30.000000000 -0400
+++ shadow/78230.tmp.16254	2006-04-28 05:43:30.000000000 -0400
@@ -0,0 +1,53 @@
+Bug#: 78230
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Blocker
+Component: Sys.XML
+AssignedTo: atsushi at ximian.com                            
+ReportedBy: apasumarthi at alliance-consulting.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Access Denied error related to deleting and accessing of .CS files generated during XmlSerialization object creation from multiple threads/processes on the same machine
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+My application uses XmlSerializer class for serializing and de-
+serializing .Net types. My application requires that I create the 
+XmlSerializer objects for the same .Net type from multiple threads and 
+processes on the same system. In such a scenario, when I run my 
+application I always get the "Access Denied" exceptions. When I look at 
+the exception stack the error looks to be around deletion and using of 
+temporary .CS files created by XmlSerializer internally. I think the 
+temporary .CS file name generation is not unique enough to handle my 
+situation.
+I get this exception on both Windows (XP/2003 server) and Linux. I don't 
+get this problem with Microsoft.Net.
+I would request you guys to look into it and fix it ASAP as my application 
+reliabillity heavily depends on XmlSerializer working correctly in the 
+above scenario.
+
+Steps to reproduce the problem:
+1. 
+2. 
+3. 
+
+Actual Results:
+
+
+Expected Results:
+XmlSerializer should work properly when creating and using objects of it 
+on the same .Net type and with the same root element tag name from 
+multiple threads and multiple processes on the same system.
+
+How often does this happen? 
+Every time I run my application
+
+Additional Information: