Or maybe we don’t. I just read that GotDotNet is going away. This is not that shocking, since the site has seemed sort of half-assed from the beginning. However, I will say that I’ve had projects that literally could not have been accomplished without GotDotNet’s help (and that of its contributors). In particular, GotDotNet was the de facto home of Stephan Gossner’s Microsoft Content Management Server code samples (that link will die soon). Of course MCMS is an end-of-life product at this point, but man there’s a lot of neat code on this site that’s suddenly going to be a lot harder to track down.
Some, but certainly not all, of this material is duplicated on various newsgroups. But often those posts link back to GotDotNet for code samples. So even if they do somehow relocate this content–at the moment there’s no stated plan to even do that–all of those links are likely hosed.
I understand Microsoft’s dilemma here, though I don’t particularly buy the “reinvest the resources currently used for GotDotNet” line. On the one hand, from a branding perspective, they can’t have this half-assed thing rusting out there in the ether with their name on it. On the other hand, they really need to keep their foot in the door in terms of community web sites, especially for developers. In terms of “resources” they want to reinvest, they can only mean people, and I’m not sure who they’re worried about (since the “Team” page is already dead), but it seems like some Microsoft people actually found this site useful.
They’re not offering any kind of plan for this phase out (they’re not even calling it a “transition”)–just a laundry list of other Microsoft developer sites. They’re chopping this thing off like a gangrenous limb. Maybe they’re assuming Google will take up the slack.
Predictably, Microsoft has backed off slightly on the self-destruct schedule for GotDotNet. And now they’re at least suggesting a path forward with CodePlex. So why the hell wasn’t that part of the plan to begin with? Possibly because GotDotNet was a repository for all the hacks and workarounds for embarrassingly poorly-designed and supported products like MCMS, products they’re trying their best to divorce themselves from.