Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage News OData.NET Is Now Open Sourced on GitHub

OData.NET Is Now Open Sourced on GitHub


Microsoft has released the source code for all OData .NET Libraries on GitHub.

The following OData-related projects are now on GitHub:

  • ODataLib
  • EdmLib
  • OData Client for .NET
  • The spatial library
  • OData Client Code Generator
  • Web API for OData
  • RESTier
  • C++ Server and Client
  • Python Client
  • OData4ObjC

The OData.NET project is organized under three branches: Master – for OData V4, ODATAV3 – maintenance for OData V 1-3, and WCFDSV4 – maintenance for WCF Data Services OData Server.

According to a team’s blog post, they have fully moved their projects to GitHub for uniformity – “No more some-on-GitHub and some-on-CodePlex”-, transparency due to “transparent planning via GitHub issues and transparent execution via commit history” and to promote involvement, promising to “actively review and merge” code contributions.

A former adversary of open source, Microsoft has been quite active in this space lately, open sourcing key pieces of their technology including .NET Core, Roslyn and ASP.NET 5. It is also interesting to note that they have embraced GitHub in spite of their own CodePlex, although the later supports git. There seems to be a trend for new projects to be open sourced on GitHub, even those coming from Facebook, Google, and Microsoft, companies which have enough resources to run their own repositories. This raises questions regarding the future of other revision control software systems such as Mercurial or Subversion.

Rate this Article


Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • TFS?

    by Mac Noodle,

  • TFS?

    by Mac Noodle,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Mercurial or Subversion ... or TFS. If i was using TFS on purpose, I'd wonder why I should still be using it.

    While Microsoft open sourcing sounds great, I wonder if those that can really do something with it (the IBMs, Oracles, Spring/Pivotal, Netflix, Facebook) are going to or will they stick with the platforms they have built on already and have contributed to the community. Even with this all open sourced, I still cannot see myself doing more with it than I have to (i.e. not by choice) until the community supports it and there is a real build/artifact management tool (no, NuGet is not even close) and things like Spring.NET and NHibernate (EF is like EJB 1/2) have new life breathed into them and are kept to the same level as the products they were born from.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p