[Mono-bugs] [Bug 76096][Maj] Changed - System.Runtime.Serialization.SerializationException: Type System.Web.Compilation.CompilationException is not marked as Serializable

[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 cmorgan at alum.wpi.edu.

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

--- shadow/76096	2005-09-16 20:35:44.000000000 -0400
+++ shadow/76096.tmp.30203	2005-09-16 21:39:41.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 76096
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: debian unstable 2.6.11.9
-Status: NEEDINFO   
+Status: REOPENED   
 Resolution: 
 Severity: Unknown
 Priority: Major
 Component: System
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: cmorgan at alum.wpi.edu               
@@ -85,6 +85,42 @@
 
 Additional Information:
 Using svn from right after 1.1.9
 
 ------- Additional Comments From gonzalo at ximian.com  2005-09-16 20:35 -------
 Please, provide any files that we might need to reproduce this issue.
+
+------- Additional Comments From cmorgan at alum.wpi.edu  2005-09-16 21:39 -------
+I saw this with a large project I'm working on that I'm not able to
+upload enough of.  I tried to break it down a bit but by using a
+index.aspx that contains only:
+
+<%@ Page language="c#" src="./index.aspx.cs" 
+Inherits="apm.SimplePage" AutoEventWireup="false" Trace="true" %>
+
+
+I get this error in html when running xsp2 on it:
+
+Server Error in '/' Application
+Parser Error
+Description: Error parsing a resource required to service this
+request. Review your source file and modify it to fix this error.
+
+Error message: Unknown attribute: src
+
+File name:
+/home/cmorgan/airsprite/scm/engineering/software/apm/exctest/index.aspx
+   Line: 1
+
+Source Error:
+
+<%@ Page language="c#" src="./index.aspx.cs" 
+Inherits="apm.SimplePage" AutoEventWireup="false" Trace="true" %>
+
+So I'm not even able to start breaking things down enough to reproduce
+this bug.
+
+This is with svn head from yesterday.  Should I upgrade to svn head
+today and try this again and open a bug for it?
+
+Chris
+