[Mono-bugs] [Bug 42989][Nor] New - User controls crash with the AutoEventwireup key word
bugzilla-daemon@rocky.ximian.com
bugzilla-daemon@rocky.ximian.com
Wed, 14 May 2003 12:56:57 -0400 (EDT)
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 tkaszuba@hotmail.com.
http://bugzilla.ximian.com/show_bug.cgi?id=42989
--- shadow/42989 Wed May 14 12:56:57 2003
+++ shadow/42989.tmp.29754 Wed May 14 12:56:57 2003
@@ -0,0 +1,63 @@
+Bug#: 42989
+Product: Mono/Class Libraries
+Version: unspecified
+OS: Red Hat 9.0
+OS Details: Fresh install
+Status: NEW
+Resolution:
+Severity:
+Priority: Normal
+Component: System.Web
+AssignedTo: mono-bugs@ximian.com
+ReportedBy: tkaszuba@hotmail.com
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: User controls crash with the AutoEventwireup key word
+
+Please fill in this template when reporting a bug, unless you know what
+you are doing.
+
+Description of Problem:
+
+When running a user control, that relies on a code behind file, which
+contains the key word AutoEventWireup="False" the compiler returns the
+following error:
+
+/tmp/tmp16d1f657.cs(82,0) : error CS0115:
+`ASP.TimeLine_ascx.AutoEventWireup' no suitable properties found to
+override
+(0,0) : error failed: 1 error(s), 0 warnings
+
+<snip>
+
+Line 82: protected override int AutoEventWireup {
+Line 83: get {
+Line 84: return false;
+Line 85: }
+Line 86: }
+
+<snip>
+
+Steps to reproduce the problem:
+1. Create a user control that contains it's code in a code behind file
+2. In the ascx file add a header similar to this "@ Control Language="C#"
+AutoEventwireup="False" CodeBehind="location of your class" Inherits="your
+web control" TargetSchema="http://shemas.microsoft.com/intellisense/ie5" %>
+3. Construct an aspx file that uses this user control
+
+Actual Results:
+Produces the error described above
+
+Expected Results:
+Should compile without a problem.
+
+How often does this happen?
+Always
+
+Additional Information:
+From my understanding this method is deprecated in the .NET framework.
+When you take it out of your user control then the user control compiles
+fine. But for people having a lot of user controls created in Visual
+Studio this would be a burden.