JChung2006 wrote:I'll ask the obvious: why not just call this RC1?
Did you watch the video?
Software people tend to get silly when it comes to versioning things: alpha, beta, CTP, RC0, version 0.041a-1. You think that you're communicating useful semantic information with these obtuse, cryptic designations when a simple version 1, 2, 3, etc. would
So again, why not just call this RC1? Release Candidate means something to me. 1 means something to me. 0 means nothing to me in terms of versioning except perhaps a peculiar reluctance to commit to something being an actual release candidate, which is pretty
much the opposite of what was said in the video.
I'd actually be gutted to have one of those cubes because it would mean that an idea I came up with was now locked up and nobody else, no other company or individual, could make use of that idea even if they had a better use for it than I did.
Sure they could... if they licensed the technology from you.
Great video! And, yes, shorter videos are excellent!
I would love to see the developer who created the XmlDataSource answer Scott's question about namespaces. Actually, I would love to hear that developer tell Scott that they intend to fix this oversight in the .NET 3.5 version of the XmlDataSource.
Then I can retire my XSL template that strips namespaces off XML documents and forget that bloody hack (my XSLT, not your code -- I like the XmlDataSource) ever existed...
Sorry, UAC stinks. Yes, running as Admin and making yourself vulnerable to all sorts of nastiness stinks worse, but that doesn't make the stench of UAC any better.
A big part of what makes UAC suck is the modal dialog box. People filter out modal dialogs eventually and just click through them regardless of the messages. The more they have to click through, the more they will.
Make RTM-quality extensions for WCF and WPF that work on Visual Studio 2005.
Otherwise, expect a significant chunk of the Microsoft developer community to look at you sheepishly because they don't have budget to drop thousands of dollars on another Visual Studio edition less than two years after they did so for Visual Studio 2005.