in

ASP.NET Weblogs

Phil Scott's WebLog

Quite exciting this computer magic

April 2005 - Posts

  • Premature Jubilation

    Oliver Sturm sent along a couple of links to his blog where he's taken a much deeper look than my "oooooooh, pretty!" reception to the new image library that is shipping with VS2005.  And after taking a deeper look at these images, I've come to the same conclusion:  ugh.

    Like Oliver said, if you want an app that looks good (or aren't creating VS2005), then you might want to venture over to glyFX or my favorite Glyfz.  It looks like Glyfz is even offering their alpha-blended PNG images for free when you buy the Office 2003 style image set.  That's a deal in a half.  Now all I need is an excuse to throw away our UI to get my boss to buy the set...
  • New Graphics with VS 2005

    Holy crap, just found these things in my Visual Studio 8\Common7\VS2005ImageLibrary folder.  In there you will find a zip file with about 800 images to use in your apps.  Unfortunately these all look to be 16x15 in bitmap format and not png or gif for the web, but hey, it's a start.  This is something I've been complaining about for years.  Should be great for winform toolbars, but not so useful for the web.

    No new icons though.  It looks like giving applications the rocket ship icon will still trendy.

    Post Script:  As I finished typing this up, this movie popped up in my RSS reader as an introduction to the VS 2005 Image Library.  Sweet!
  • Validating XHTML with ASP.NET 2.0

    With the go-live of ASP.NET 2.0, I've been actually using it at a level of more than "ooh, pretty new feature." I'm kinda of a standards nerd, so naturally I've been messing around with the XHTML output and making sure I like what I'm seeing.  So far, so good. But I ran my page against the W3C's validator and it freaked out, complaining about form tags having names and the such. So I take a look at the source, and it looks good to me. So I go back to the validator, and run it one more time, this time enabling "Show Source." Ah, there's the problem. ASP.NET thinks that the validator is some ghetto browser from 1996 so it is sending it invalid markup.

    The fix was pretty easy once I tracked it down. Simply update the browseCaps section of your web.config to tell ASP.NET about the W3C's user-agent. Here's the code I'm using:

    <case match="W3C_Validator+">
       browser=Netscape
       frames=true
       tables=true
       cookies=true
       javascript=true
       javaapplets=true
       ecmascriptversion=1.5
       w3cdomversion=1.0
       css1=true
       css2=true
       xml=true
       tagwriter=System.Web.UI.HtmlTextWriter
    </case>

    Now when you validate your page, ASP.NET will send out the same HTML as it would if Firefox or IE were requesting the page. Now what I'd really like to do is tell ASP.NET to shove it, and spit out XHTML on unknown browsers. Anyone have any ideas?

More Posts