You don't think MS are holding back  do you ?

Both those two you sent me were written by them, and got all the way round the block till the last hurdle, where they fell.

The one from DotDotNet takes an image  and the goes through replacing pixels with characters and making  a table, then ouputs the table as html.
Absolutley useless concept - like a bike with square wheels.

The other one may be a little better, a httphandler than handles requests.
Basically this one takes a <img src="somestring"> where "somestring" is a an url  to a page  containing code writing an altered image to Response.Output stream.

I may be able to wangle and twist this second one into doing something maybe a little more up my street, i.e. make that httphandler handle requests from server  code, i.e. if a control  wants an ImageUrl then set it to an url that will generate the image - BUT without the physicallity and the overhead of an aspx  page, I think ... maybe I can write a httphandler to handle it all internally within my dll, will have to fool the control into thinking it's an url that's all.