Skip to main content

Awarded Team System MVP

A little more than a month ago, I was awarded the Microsoft Most Valuable Professional (MVP) Award for Team System. I haven't said much about it because I try to remain a humble guy and frankly, I've been swamped with work/life. And, unlike a lot of awards, it's not really one you "go after"...it comes to you without a formula.

What I really want to say about this is thank you. Thank you to the community for creating opportunities to present. Thank you to Microsoft for supporting technology professionals and creating jobs and careers around your products (and staying out of the way when I comes to implementation :). Thank you to the community leaders and professionals who dedicate their time and seemingly endless energy to making all of us stronger by creating environments of intense learning and camaraderie. Thank you to my employer for believing in my endeavors and investing in me the time to develop my TFS/VSTS skill set and share what I learn with the community and clients. And finally, I want to thank you--the readers/community/professional folks. Thanks for showing up to presentations, seminars, user groups and conferences. It’s a blast!

I'm humbled even to be mentioned in the same sentence as some of the past and current MVPs. While the MVP is quite an honor, it's not a means to an end. I'm still the same guy. I plan to keep doing the same sort of things I was doing before. To that end, please let me know how I can help you with learning or adopting TFS/VSTS in your environment. If you know me, I'm not completely bias toward TFS...there are other great tools for the job out there. We'll help get you up and running and producing high quality software--regardless of toolset.

Technorati Tags: ,,,,

Comments

insurance man said…
"Microsoft Most Valuable Professional (MVP) Award for Team System" Congratulations, this is a big deal. ken
Go Big Ten
Roland said…
Don't be fooled by the rocks that I got, I'm still Jeff from the block.

Popular posts from this blog

Get Your Team Foundation Server Hate On!

[Google ranking skyrockets... ;-)] I'm a big fan of TFS/VSTS. However, there are a good pocket of folks who take issue with the way TFS handles or implements a certain feature. Well this is your chance to vent! I'm planning a presentation around the "Top 10 TFS/VSTS Hates and How to Alleviate Them"...or something along those lines. But I need your help. Post a comment below detailing your dislike. If it's legitimate, I'll highlight it in the presentation and [hopefully] provide an alternative, resolution, or work-around. Thanks in advance! Update 7/19/2008: Version Control and Microsoft

Rollback a Ooops in TFS with TFPT Rollback

Rhut roe, Raggie. You just checked in a merge operation affecting 100's of files in TFS against the wrong branch. Ooops. Well, you can simply roll it back, right? Select the folder in Source Control Explorer and...hey, where's the Rollback? Rollback isn't supported in TFS natively. However, it is supported within the Power Tools leveraging the command-line TFPT.exe utility. It's fairly straightforward to revert back to a previous version--with one caveot. First, download and install the Team Foundation Power Tools 2008 on your workstation. Before proceeding, let's create a workspace dedicated to the rollback. To "true up" the workspace, the rollback operation will peform a Get Latest for every file in your current workspace. This can consume hours (and many GB) with a broad workspace mapping. To work around this, I create a temporary workspace targeted at just the area of source I need to roll back. So let's drill down on our scenario... I'm worki

Shrinking WSS (Sharepoint) SQL Server Log Files

Yesterday, while migrating a source repository from StarTeam to TFS, I received the following error: "TF30042: The database is full. Contact your Team Foundation Server administrator." Excuse you? Sure enough, my 100+ GB drive was full on the server. But I'd only migrated around 1000 items. Surely SQL wasn't consuming 100MB per file. Turns out (yes, there was a lot of crud on the drive but...) the majority of the space, almost 40GB was being consumed by the Windows Sharepoint Services WSS Content data and log SQL Server files. Huh? I still need to investigate and understand why this portal, which is 100% unused, grew so large. Regardless, here's what I did to resolve: Since this is not yet a production database, I flipped the SQL recovery option from Full to Simple for WSS Content and several other databases. Detail here and here . Executed the maintenance plan for all the databases to get backups and clear out some of these files. That didn't help much. T