CodePlex
Web-based collaborative software platform
title: "CodePlex" type: doc version: 1 created: 2026-02-28 author: "Wikipedia contributors" status: active scope: public tags: ["project-hosting-websites", "microsoft-websites", "discontinued-open-source-software-hosting-facilities"] description: "Web-based collaborative software platform" topic_path: "general/project-hosting-websites" source: "https://en.wikipedia.org/wiki/CodePlex" license: "CC BY-SA 4.0" wikipedia_page_id: 0 wikipedia_revision_id: 0
::summary Web-based collaborative software platform ::
::data[format=table title="Infobox website"]
| Field | Value |
|---|---|
| name | CodePlex |
| caption | CodePlex homepage |
| url | |
| commercial | no |
| type | Forge |
| registration | Optional |
| language | English |
| owner | Microsoft |
| launch_date | |
| current_status | Offline |
| :: |
| name = CodePlex | caption = CodePlex homepage | url = | commercial = no | type = Forge | registration = Optional | language = English | owner = Microsoft | launch_date = | current_status = Offline CodePlex was a forge website by Microsoft. While it was active, it allowed shared development of open-source software.{{Cite web |url= https://spectrum.ieee.org/social-networks-for-engineers |title= Social Networks for Engineers |author= Sue Karlin |publisher= IEEE.org |date= 2011-06-06 |access-date= 2011-06-17}} Its features included wiki pages, source control based on Mercurial, TFVC, Subversion, or Git, discussion forums, issue tracking, project tagging, RSS support, statistics, and releases.
While CodePlex once encompassed a wide variety of projects, including SQL Server, WPF, and Windows Forms-related projects, its major activities were focused on .NET Framework (including ASP.NET) and SharePoint. The most prominent and used project that was born inside CodePlex, the AJAX Control Toolkit, is a joint project between the community and Microsoft.
History
The initial beta started in May 2006, with the final release a month later in June. A new version of the website was released every three weeks adding additional features and updates.
In 2010, an unrelated CodePlex Foundation was renamed Outercurve Foundation to clear up confusion that there was a direct relationship between the foundation and CodePlex, which is solely owned and run by Microsoft.
Since January 22, 2010, Mercurial distributed source control system has been supported as well, and this support has been enhanced. On March 21, 2012, CodePlex announced the support of Git as a source control option.
On March 31, 2017, Microsoft announced the discontinuation of CodePlex. The original plan was to make CodePlex read-only in October 2017 before finally shutting it down on December 15, 2017. Microsoft partnered with GitHub to allow projects to be migrated to the service. An archive was available as a lightweight site to browse the projects that remain, in a read-only mode. The projects could be downloaded or transferred to GitHub or a similar place. Microsoft finally shut down the archive on October 21, 2021.
References
References
- ""The CodePlex Foundation Rebrands, Renamed Outercurve Foundation"". Outercurve.
- "CodePlex now supporting native Mercurial". Microsoft.
- "Associating Change sets to Releases and Displaying Mercurial Branches/Tags". Microsoft.
- "CodePlex Mercurial Support for Forks". Microsoft.
- "git commit –m "CodePlex now supports Git!"". Microsoft.
- Bright, Peter. (22 March 2012). "Microsoft brings git support to its CodePlex hosting service". Ars Technica.
- Harry, Brian. (March 31, 2017). "Shutting down CodePlex". [[Microsoft]].
- Krill, Paul. (April 3, 2017). "Microsoft to shut CodePlex open source project site". [[IDG]].
- Duckett, Chris. (April 3, 2017). "Microsoft takes CodePlex to death row on back of GitHub monoculture". [[CBS Interactive]].
- "CodePlex". Archiveteam.
::callout[type=info title="Wikipedia Source"] This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page. ::