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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=78797 --- shadow/78797 2006-12-28 02:07:54.000000000 -0500 +++ shadow/78797.tmp.6404 2007-01-23 22:37:14.000000000 -0500 @@ -1,12 +1,12 @@ Bug#: 78797 Product: Mono: Class Libraries Version: unspecified OS: unknown OS Details: -Status: NEEDINFO +Status: REOPENED Resolution: Severity: Unknown Priority: Normal Component: Sys.Web AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] @@ -58,6 +58,37 @@ Additional Information: using latest mono from svn as of July 8, 2006 ------- Additional Comments From [EMAIL PROTECTED] 2006-12-28 02:07 ------- Please, attach a simple test case that reproduces the problem. + +------- Additional Comments From [EMAIL PROTECTED] 2007-01-23 22:37 ------- +Thanks Gonzalo, this appears to be resolved. Controls registered in +web.config now are properly handled on pages that do not specifically +regsiter them. + +However, I did notice that if you do not specify the control properly +in the page, the error message is different from the MS implementation. + +For example, in web.config, I have an entry such as: + +<add tagPrefix="mm" tagName="xx" src="~/controls/MyControl.ascx" /> + +If in a page I make a mistake and try: + +<mm:asdf runat="server" /> + +The error message in mono that comes back is: +TagPrefix mm not registered + +This is a bit misleading as the tagprefix is actually correct - it is +the tag name which is wrong. The MS implementation shows an error +message as follows: + +"Unknown server tag 'mm:asdf'". + +This would probably be better, as it does not give an incorrect error +message. + +Thanks, +Mike _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
