Archive for August, 2009
Last week I talked about a situation where the previous programmer had placed the body tag inside the ContentPlaceholder in order to allow for a different body tag on the page.
Since this is a project that I am actively involved in, I’ve been thinking about the easiest way to “fix” the code so that we can use it.
My post yesterday about an easy way of implementing templated e-mail was met by a comment suggesting that using XSLT would allow for more flexibility. Which is true. Once it was suggested, I started asking myself, “but is it the BEST method of implementing templated e-mail?”
I think, as programmers, we tend to think that having more options, having more flexibility, using the latest and greatest technology, is always best. But is it?
One thing I’m pretty consistent about is letting the computer do most of my work for me. As a “programmer” I really don’t like to program. I prefer to solve problems.
You’ve already seen the effects of this in how I program PDF files where I use form fields and fill them at runtime rather than building up the entire PDF at runtime.
I use a similar technique when creating e-mails to send out from ASP.NET.
Here’s what I do
One of the companies I work for recently took over a project from another vendor. As we started to maintain the site, we noticed that we could not drag and drop controls onto the page and get any more than a stub of the control. <asp:hyperlink runat=”server”></hyperlink> is ALL we got when we dropped the hyperlink control onto the designer.
In fact, every ASPX control on the page displayed the error, “Unrecognized tag prefix or device filter ‘asp.’”
What’s up with that?
Thinking that there must be something wrong with our development environment, or at least something wrong with how we have the project configured, I started my search on Google.