To specifically address the points raised, the fact that something is open source does not automatically elevate it in priority for this project. Quite a few of us work for companies that make heavy use of Visual Studio and appreciate all the functionality in it. The fact that the source code for CB is available actually doesn't add much favor to it when we evaluate which tools to support. Our primary concern is what tools can we use and what does the job the best. Of the IDEs we can use, there's quite a few, ranging from VS to CB to even Eclipse and Netbeans. The one that would to the job the best, in our view, is VS, so we will choose it. If few people on the team even touch CB or the other IDEs, then there is little motivation to continue supporting it, especially if that support was broken to begin with. You claim there is a strategic reason to provide support for open source platforms. In this instance, the project feels that that strategic reason is not important enough to merit continued effort. If you feel strongly enough to try and make it work, then go for it, but the rest of us aren't terribly bothered by not having access to VS' source code.