.NET Goes Open Source

.NET Goes Open Source

150 150 admin

net logo

Big giant news from S. Somasegar, corporate vice president of the Developer Division at Microsoft, announcing .NET going open source.

Open source is discussed at CSW every time we have a chance to work with a new technology, or when software releases come out. The open source movement, concerning development models, promotes a universal access via a free license to a product’s design or blueprint, and universal redistribution of that design, including subsequent improvements to it by anyone.

In this case, the news include opening access to .NET and Visual Studio to a broader set of developers by open-sourcing the full .NET server core stack and introducing a new free and fully-featured edition of Visual Studio.
With these releases, Microsoft is broadly opening up access to its platform and tools to every developer building any application in today’s mobile-first, cloud-first world.

Opening up access to Visual Studio extensibility to a wider audience also creates great new opportunities for extension authors to build new tools and experiences on top of the Visual Studio platform. This wider audience includes community members (developers) engaged in building code collaboratively.

This announcement is big news because it draws attention to an issue that Microsoft had been ignoring for years. The company knows the world revolves around developers, so they’re ready to appeal to the developers they’ve been missing–the PHP, node, and Ruby developers, for instance.

Another reason is the potential to spur independent innovation around Microsoft.
If you do a bit more research (or jump in one of our discussions), you’ll know that there was a time when executive Microsoft critiqued the movement, so opening the door for change is noteworthy.

You can explore the range of .NET open source projects via GitHub (their new home) here; oh hey, remember our post on Git vs GitHub?

It is Microsoft’s intent to enable startups, students, hobbyists, and developers (no matter the platform they are targeting or the app they are creating), to be able to build for today’s mobile, desktop, web and cloud platforms.
It is our intent to give it a try, keep our eyes open, and follow up with another post in the very near future. See you then!