https://blogs.msdn.microsoft.com/visualstudio/2016/03/17/ope...
> The repository currently contains a subset of all extensions in Productivity Power Tools for Visual Studio 2015. Some extensions are not yet ready to be open-sourced, but we’re working on making all of them available over time.
Uh, there's only one user bitching. Everybody else seems fine with it.
I'm not bitching about anything. I'm providing a contrary view to the effusive and largely uncritical praise that much of the tech press spews whenever MSFT announces that they've open sourced this tiny thing, or ported a part of that thing to a non-Windows OS.
If you read my other comments elsewhere on this page, it becomes clear that I very much want for MSFT to have stopped bullying, subverting (and impeding the function of) standards bodies, engaging in anticompetitive lock-out, and other such shady backroom dealings. MSFT is a big company that hires rather smart people. They could use their money and collective brainpower to do really great things for the computing community.
Thing is, those of us who've been around for at least the past twenty years have seen the "Good Microsoft" act, and we remember how that act was rather short-lived. If MSFT were to do something substantially significant (such as joining the OIN [0], making a public promise to remain a member and substantially participate in its proceedings for the next twenty years, as well as a public promise to never tamper with it or its proceedings [1]) before many of us old hands start thinking that this is an actual change in corporate direction.
[0] http://www.openinventionnetwork.com/
[1] That is, to never, ever do anything even remotely like the shit they did at ISO.
I genuinely hope that the corporate overlords within MSFT are very serious about becoming a good actor in the computing community. MSFT is a big company, and they could do a lot of good for both the software and hardware sides of the community.
However, this is far from my first rodeo, and this isn't the first time we've seen MSFT play the good guy. If they stick to form, the community that they fostered will be forcibly forgotten and left to wither in the sun in a -comparative- blink of an eye. Just ask the Samba guys about those Plugfests they used to attend. :)
1. Use samples that each explore an isolated feature. Available on github [0] or for a few years back on MS website.
2. Decompile VS to see what's happening behind the scenes. While .NET Reflector does very fine job, the code was convoluted to begin with and it was nearly impossible to find relevant bits.
I imagine engineers at MS are cleaning up the code of all power tools so that it's clear and easier to follow.
For example we have "Go to definition" right here [1] and I remember long evenings unsuccessfully looking for this functionality in the decompiled code.
[0] https://github.com/Microsoft/VSSDK-Extensibility-Samples
[1] https://github.com/Microsoft/VS-PPT/tree/master/src/GoToDef
sigh All significant wars are much larger than the individual actions in them. :) Read my other comments attached to this HN submission to get some insight into my opinion of MSFT and its actions. It's probably a little more nuanced than you'd expect.