.NET Framework SDK rocks.. or does it? :)
<stretch....> after several months hibernation, I've dusted off my blog. The new MSDN viewer is now being developed by another team, and I've moved away from doing design on that full time, and am now a consultant on that project. <another way of saying I dont really do any work on this project other than complain about other peoples designs, but get to put it in my weekly status reports.. when i get around to sending them.>
But.. I'm back to my regular day job now... driving the Whidbey SDK. Hopefully some of you reading this will have had a chance to download the Beta 1 redist and SDK from http://lab.msdn.microsoft.com/vs2005/downloads/default.aspx If you think it rocked, or sucked, well I'm the person you should be yelling at. The biggest problem managing the SDK is that we get such little feedback on it. We do get feedback but it generally tends to focus on API or product questions, as opposed to the content of the SDK (why dont you have xyz sample! How do I use this tool? Why dont you have abc tool? Why do the docs for blah API suck, what the heck are the Quickstarts? are all questions I'd love to hear).
So if you did get a chance to test drive the beta (and I know it's not in great shape, it's our first beta and we're re-doing large portions of it), please let me know what you thought, and if you didnt check it out yet, well what ar eyou waiting for? <insert snake oil salesman pitch here> :)
