Telerik is a new sponsor. Check out their UI Suite of controls for ASP.NET. It's very hardcore stuff. One of the things I appreciate about Telerik is their commitment to completeness. For example, they have a page about their Right-to-Left support while some vendors have zero support, or don't bother testing. They also are committed to XHTML compliance and publish their roadmap. It's nice when your controls vendor is very transparent.

As I've said before this show comes to you with the audio expertise and stewardship of Carl Franklin. The name comes from Travis Illig, but the goal of the show is simple. Avoid wasting the listener's time. (and make the commute less boring)

Note that for now, because of bandwidth constraints, the feeds always have just the current show. If you want to get an old show (and because many Podcasting Clients aren't smart enough to not download the file more than once) you can always find them at http://www.hanselminutes.com.

I have, and will, also include the enclosures to this feed you're reading, so if you're already subscribed to ComputerZen and you're not interested in cluttering your life with another feed, you have the choice to get the 'cast as well.

If there's a topic you'd like to hear, perhaps one that is better spoken than presented on a blog, or a great tool you can't live without, contact me and I'll get it in the queue!

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

Dear Scott,Thanks for an excellent show. When doing the DNRTV on Continuous Integration kindly start at the very basics, like how does one setup the miniumum required to get Continuous Integration up and running. Show a very simple example. This will help me and probably a lot of others who feel themselves a little left behind on continuous Integration./morten

You mentioned on this show that you produced Virtual Machines that your latest built installation package is automatically deployed to. I really like that idea.

Could you provide little more detail as to how that works in practice?

1. How much space do you typically eat up before you have to start archiving (how many versions of the VM do you keep around)?

2. How long does your build process take? It would seem to me that bringing up VMs would take a significant chunk of time. I like to keep our builds <10 minutes, including all the errata like Coverage, FxCop, etc, so that feedback to developers is more immediate.