I'll make sure to include some example output in my next article. It's pretty readable - not quite idiomatic C#, but you can almost always see what's going on. It's very conservative C#, and it still uses the same style of coding that the original source used - ADO and `Response.Write`, rather than WebForms or ASP.NET MVC.
This project had the full support of the company, from our newest hires all the way to Joel and Michael. As many people have noted, using this wacky one-off language was a source of a lot of friction in our business, and we felt that spending a few months to get rid of that friction would be a good use of resources (me).
This project had the full support of the company, from our newest hires all the way to Joel and Michael. As many people have noted, using this wacky one-off language was a source of a lot of friction in our business, and we felt that spending a few months to get rid of that friction would be a good use of resources (me).