>But you're right, that clearly the "devs" have preferences. The problem with your mechanism is that they don't express them to you in customer service requests. They just job-hop to another environment, doing Javascript work, or Linux, or Ruby. And you never hear from them.
>Basically, the way feedback works in this world is with feet, not bug reports. If you build it they will come. If you don't they will leave.
Is there any quantifiable metric to measure this so called exodus beyond anecdotes and the ".NET is dying" posts on here?
If there was an IDE for .NET on par with VS, it will definitely see uptake regardless of suits.
> As usual, there’s so much I will only be able to just skim the surface with this post. Stay tuned for many more posts on my blog, the ALM blog, the Visual Studio blog and others as we reveal more detailed information about all of the new capabilities.
>I will not, in this post, be talking about many of the new VS 2013 features that are unrelated to the Application Lifecycle workflows. Stay tuned for more about the rest of the VS 2013 capabilities at the Build conference.