First Source Code for .NET Framework Libraries Released -- Visual Studio Magazine

News

First Source Code for .NET Framework Libraries Released

Microsoft releases .NET 3.5 Framework library source code.

By Becky Nagel
02/01/2008

Microsoft has followed up on its promise to release the .NET 3.5 Framework library source code.

Libraries Now Open

A list of what's available for developers to view:

.NET Base Class Libraries (including System, System.CodeDom, System.Collections, System.ComponentModel, System.Diagnostics, System.Drawing, System.Globalization, System.IO, System.Net, System.Reflection, System.Runtime, System.Security, System.Text, System.Threading, etc.)
Windows Forms (System.Windows.Forms)
Windows Presentation Foundation (System.Windows)
ADO.NET and XML (System.Data and System.Xml)

Source: Microsoft

The company released the source code of more than a dozen libraries -- including ASP.NET, Windows Presentation Layer, Windows Forms and the .NET Base Class Libraries -- last month (see "Libraries Now Open").

Scott Guthrie, general manager of the Microsoft Developer Division, is promising that more libraries will come soon, including ones for Workflow, Windows Communication Foundation and LINQ.

"We think that enabling source code access and debugger integration of the .NET Framework libraries is going to be really valuable for .NET developers," he says in his blog post announcing the release of the class libraries. "Being able to step through and review the source should provide much better insight into how the .NET Framework libraries are implemented, and in turn enable you to build better applications and make even better use of them."

His blog includes instructions for configuring Visual Studio 2008 to access and debug the source code.

While the source code is being released under the company's read-only reference license (as originally planned), Guthrie notes Microsoft has made a change to the license terms.

"When we announced that we were releasing the source code back in October, some people had concerns about the potential impact of their viewing the source," notes Guthrie. Now, if a developer is coding for the Windows platforms, "You can look at the code, even if that software has 'the same or substantially the same features or functionality' as the .NET Framework," he says.

About the Author

Becky Nagel serves as vice president of AI for 1105 Media specializing in developing media, events and training for companies around AI and generative AI technology. She also regularly writes and reports on AI news, and is the founding editor of PureAI.com. She's the author of "ChatGPT Prompt 101 Guide for Business Users" and other popular AI resources with a real-world business perspective. She regularly speaks, writes and develops content around AI, generative AI and other business tech. Find her on X/Twitter @beckynagel.

Printable Format

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.