Why are we open sourcing our extensions?

We plan to open source many of our solutions, listed on library of tooling and guidance solutions, to share them as sample code, foster community collaboration and innovation.

Our mission is to “provide professional guidance, practical experience and gap-filling solutions”. When we ship a solution, we need to switch context to other gaps, limiting our ability to effectively invest in long-term maintenance and innovation.  By embracing open source, we hope to enable the community to review the solutions, help fix bugs and contribute features they need. 


Our open source solutions

2016.09.08 – Add latest OSS projects.

… more to come!

What are your thoughts on open source?

We look forward to hearing from you. Here are some ways to connect with us:

Comments (5)

  1. WouterdeKort says:

    I think the open sourcing is great. Hopefully others can learn from our work and I really hope that the community will help maintaining and extending these projects.

    Thanks Willy!


  2. Sturla says:

    Any change you can pull this (or something like it), Export Template Wizard , to be open sourced? https://visualstudiogallery.msdn.microsoft.com/57320b20-34a2-42e4-b97e-e615c71aca24

    Its from Visual Studio Product team but has not been touched since 2010. There is like nowhere I can find documented information about how you should do a multi-project-solution. This is probably the best thing I have found so far but I´m having problems with VSIX and PCL.. https://github.com/ligershark/side-waffle/wiki/How-to-create-a-multi-project-template

    1. Sturla, at this stage we are only considering to open source projects we own.

  3. Art Manuel says:

    Can you guys change this page (https://blogs.msdn.microsoft.com/visualstudioalmrangers/2015/04/22/library-of-tooling-and-guidance-solutions-aka-msvsarsolutions/) so that instead of a blog post masquerading as a web page, maybe it is an actual web page? Maybe a static website running on GitHub or something.

    1. What’s your concern with the current solution page, which is intentionally using our team blog?

Skip to main content