Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Dec 08, 2005 07:44 AM by monolithx
Dec 06, 2005 08:26 PM|LINK
I've created a cusom version of the form class according to Scott M.
I did compile DLL that contains it and put it to reference, and also referenced it on the page I'm using it on.
Still, although it all compiles and works like a charm at runtime, my design editor is broken and reports strange error against all logic as on the picture:
Dec 07, 2005 02:34 PM|LINK
I've seen this problem also. Visual Studio 2005 doesn't like any control derived from HtmlControl or any of it's descendents. It seems quit happy if the control derives directly from Control or WebControl. I remember this same basic behavior in VS2003
Makes overriding the form tag a real pain. It appears that Scott Mitchel did his article w/o using VS.
If anyone knows how to make an HtmlControl based user control acceptable, I would love to know!
Dec 07, 2005 04:54 PM|LINK
Finally some echo.. :)
Thx m8, now I'm sure it's not all my fault.
Well, strange how there is zero audience from MVPs or ASP.NET Team on this matter.. actually on the matter where Microsoft really screwed up. Doh....
Dec 07, 2005 11:55 PM|LINK
After a little digging I found that there is a documented bug on the MSDN "Product Feedback Center".
It seems that, by design, there is no support for rendering and HtmlControl based controls inside the IDE. Since HtmlForm derives from HtmlControl, not only do you get the error indication, nothing on the page will render (since all other controls are childern
of the form control).
They have recently marked this bug as re-activated for possible fixing in the next version of VS - when ever that is.
Net, if you want to remap URLs and use the IDE, you really need a different solution than overriding HtmlForm.
Dec 08, 2005 07:44 AM|LINK
Tragedy is that the bug was reported for Beta1. They could've fixed it by now.
Well, as the form I use is just to fix postback bug, I find it appropriate to just use normal form on all pages until production development. That way I think I'll have no problems... I hope...
O maybe write a http module/handler to override action attribute of the form control...