The team is back! The team is back! And with a blog. Mike Champion, who was a recent MS hire, started the XML Team blog along with his own blog on MSDN. Very cool, and thanks for listening. He also has a cool title, "Program Manager - XML Standards". Good job Mike, and we look forward to hearing from you and the team.
Is Arpan back? Hopefully.
I hope other teams don't follow this trend.
Special Kansas City .NET User Group Meeting - December 16th
Location: Microsoft Kansas City Office
Time: 6:00PM - 7:30PM
Topic: Software in a Service-Oriented World
If services are the next big thing—and they are—what impact will this change have on software development? David Chappell will give a perspective on this question, focusing on the impact this move will have on .NET. Drawing from his forthcoming book on Indigo, David will describe how this new technology fits and what it does, and he’ll explain why BizTalk Server is becoming a central technology for .NET developers to understand. The goal is to give a clear sense of what a developer’s life will be like in this brave new world.
Presented by: Dave Chappell
Dave is Principal of Chappell & Associates in San Francisco, California. Through his speaking, writing, and consulting, David helps information technology professionals around the world understand, use, market, and make better decisions about enterprise software technologies. http://www.chappellassoc.com
Well it's announcement time. We are in the process of partnering with Microsoftbookstore.com to form the Developer Book Club, formerly known as .NET Book Club. With this name change comes a reformation of the club itself. An online forum community for books is a utopia, but only brings advantages to participants, and they were few and far between. Instead, we are focusing on the message. We want to have the authors interact with the community about the book. We will have a monthly webcast for the featured book of the month with the author. MSDN Webcast is generously hosting these for us, and I hope you will join us. The webcast will be made up of three sections. The first, John Alexander and I will interview the author about topics that will help you understand the author further beyond the words written. We will discuss the relative topics of the book and try to keep the banter down to a minimum. After this, the author will hold a 30-45 minute session on the topics of the book and so you some demos pulled out of the book. Then finally, you will be able to interact with the author for a Q&A session. These webcast will be on-demand available so if you can't attend live, you can still download them later. Are you as excited about this as I am? I hope so.
The first webcast is next week with Bill Evjen, discussing his book: ASP.NET 2.0 The Beta Preview. The date is Tuesday the 14th and we will start at 8:00 AM PST. I know it is a little early for you west coast folks, but just in time for lunch on the east coast. Let me know what you think of the concept and I hope to see you there!
First off, I want to start this post with an 'Arrrggggggg!!!!!!'. Much better. I have an Inspiron 8600 from Dell. The machine is awesome, I have never had a laptop that ran so fast. It is the perfect machine for a consultant who has to travel to the client site, but still come home and dock that machine to work. So what is the issue? Well you remember I said I get to come home and dock the machine. Well in October, right before a trip to Redmond, my machine decided that it didn't ever want to be away from it's dock and did not boot unless it was docked. I would receive the friendly error:
The computer is docked and only battery power is detected.
This can happen if the power adapter is unplugged,
or the computer is not properly connected to the
Joy oh joy, that experience was fun. The solution after making one tech cry and another hangup on me, I got a tech to send me a box to send the machine back to them and they replaced the system board. TEN DAYS Later, they shipped the machine with new board and everything was good again.
Fastforward to today. I have plans to be onsite with a client tomorrow. I have pulled my VPC on the machine and decided to watch a movie with my wife while I finish up some extra work. I disconnect the machine from the docking station and proceed to go downstairs. Once I arrive, I boot up the machine to get my lovely error message again. You got to be kidding me, one month after spending 13 days without a laptop (3 days to arrive last time) I have to do this process all over again. S#IT!!!!!! So I get Dell back on the phone, and one hour after disconnecting the machine from the docking station and plugging it in with every possible scenario, they want me to send my machine back to them for another "10 or so days", so they can replace the system board again. This time is different though they kept telling me, because they are going to look at the docking station too. Ohhhhhhhh, the docking station is what I said. I told them to send me a limp along machine so I can WORK, but Dell doesn't do that for customers. So I will ship them my machine once more. They will replace the system board and I will blog to you again on January 9th about my machine crashing. I am calling them tonight again to see if it's possible to have them extend the warranty for a little longer to ensure this doesn't happen again. Probably have no luck, but it is worth a try.
The moral of the story is, stay away from the Inspiron 8600 and Latitude m60 (same board) if you plan to dock, because you will probably get a crappy machine and will only have it for 20 days of each month, but Dell won't care. You think after they replace the $700 system board twice, it might be cheaper to just send a new machine for the long haul.
Looks like someone has pointed VBSucks.com
to the MSDN C# Developer Center.
Irwin Dolobowsky has recently taken over the XML Developer Center at MSDN with many promises of a new center for XML developers. During his self admitting 2 or 3 "first post" entry, he states a few items he is going to do to make the dev center better. This post took place a month ago, and here are some results.
Bring out the MVP's - Being one of the few MVP's in the area of XML, I can say that I have not been contacted on this front. I am guessing the functionality is there for this, since the other dev centers have this.
Bring out the Team - As I stated last week, the XML team has gone underground. Where is this team, now that Mark and Dare are gone? People were starting to understand the importance of System.Xml education with the posts from Dare and Mark explaining the different stores and APIs. It seems that since the announcement of all the cuts of functionality, the team ran for cover and hasn't looked to see if the smoke has cleared. Well it has. We know that DOM isn't dead, and don't have many options when it comes to XQuery support by Microsoft outside of SQL Server, so come on out.
The Latest and Greatest - It's December and the latest article posted was October. Mark's MSDN Video was posted, but that is clearly not the latest and greatest with the old content discussed. A perfect article to update is Mark's article on the System.Xml 2.0 features. This shouldn't take much time, but would be interesting to read to ensure everyone knows what isn't going to be in there, compared to what was announced at PDC and in Beta 1. Do you guys need help in this one? Maybe if you actually worked on the first point, we might be more willing to help you out.
I am not trying to pick a fight, I just wish somethings that are said will get done.
In this episode of MSDN TV
Mark Fussell, former Lead Program Manager of the WebData XML Team, talks about XML features of Visual Studio 2005. Inside of which he talks about the XPathDocument being editable and XQuery support and we know that is not
going to happen. The show is basically based on his article that needs to be updated
, but that is doubtful since everyone on the WebData XML Team either left or has went back into an unknown hole to not be found. That is another problem for another day (not people leaving, but who is left and where are they?). If I was on the XML team, I would suggest this MSDN TV be edited or attach a disclaimer about the no longer valid statements that are made in this video.