GotDotNet Shuttered -- Visual Studio Magazine

Desmond File

GotDotNet Shuttered

Looks like Microsoft decided to shut down the GotDotNet Web site. According to Microsoft, the move is intended to eliminate redundancies with other Web resources and reflects declining traffic on the site.

The Partners, Resource Center and Microsoft Tools have already been shuttered, and Private workspaces, Team pages and Message Boards will be next on March 20. By April, the GDN CodeGallery will be dark. The whole schmear will fall offline on June 19, according to the projected schedule.

The decision is hardly a surprise. Microsoft has put its weight behind CodePlex and wants to make sure that subset sites like GotDotNet aren't robbing it of momentum.

Check out a nice synopsis of the history of GotDotNet and its eventual demise at the .NET Sweatshop (v2) blog.

Posted by Michael Desmond on 02/28/2007

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.