[OWASP-WEBGOAT]RE: C# conversion fun in webgoat.net
tim.aranki at dev-quest.com
Mon Aug 4 21:30:15 EDT 2003
I have not done a real compare, but what about the
System.Web.UI.HtmlControls namespace? It has implimentations for all
the HTML elements... The props/methods may be different, but it would be
better/faster than re-writing ECS.
There is also a System.Web.UI.HtmlControls.HtmlControl object that we
can subclass if needed (if there is an element missing, for example).
From: Andrew van der Stock [mailto:avanderstock at b-sec.com]
Sent: Monday, August 04, 2003 8:05 PM
To: 'Jeff Williams @ Aspect'; 'Mark Curphey'; 'Bruce Mayhew'; 'Harbar,
Spencer'; owasp-webgoat at lists.sourceforge.net
Cc: 'Tim Aranki'
Subject: C# conversion fun in webgoat.net
I've been working on conversion of the goat using the source Mark
provided to me last week.
We have a small problem in that the code makes extensive use of Jakarta
Element Construction Set, a nice method to do markup without using
dropouts to HTML source (a la PHP or old ASP).
However, it is *everywhere* through the code, and it uses various
subclasses such as IMG and so on.
There's three alternatives:
* port ECS (Hard(TM))
* develop an alternative lightweight framework that is good enough
* find a way to emulate it so a global search and replace will do the
The right way? I don't know. I think it'll be faster to work on a hack
in .NET to emulate it, but I'd be interested in your feedback.
More information about the Owasp-webgoat