""Drag and Drop, IDE's might have initially been invented to enhance productivity, but their main effect was to dumb down the discipline."
But isn't that where most of the productivity gains can be found in .NET?"
No, that's the productivity gains of *Visual Studio*. .Net is NOT Visual Studio. Visual Studio is a great IDE, and truly dumbs down programming. The .Net Framework is something else completely. Here are some ways in which moving to .Net makes you more productive:
* It is a huge set of libraries encompasing nearly every Windows API in a standardized, understandable way, letting you quickly access functionality that used to be a ton of hard work to use.
* It compiles any .Net language down to a standard language (the .Net CLR), which means that a function or object coded in one .Net language can be used in another .Net language with zero translation needed. All .Net languages map their types and objects to the .Net CLR, which means that even a goofball language like F# can be used to write a particular function for use in another app.
* Visual Studio is a great IDE. Yes, it has "dumbed down drag 'n drop" programming in it, and with IntelliSense, you basically can guess your way through a project. It also has an excellent debugger, brings together data (even from non-Microsoft sources, such as MySQL) extremely well, has a built in profiler, test units, and manages projects much better than Visual Studi 2003 did, let alone that piece of junk Visual InterDev.
* The .Net versions of languages make much more sense than their previous versions. I would rather code in VB.Net than VB6, because VB.Net was rewritten from the ground up, instead of slowly accumlating new concepts and structures on top of a poorly designed language to begin with. C# is pretty good too, although I rarely write code in it.
I could go on and on. But to conflate drag 'n drop programming with .Net itself is a fallacy that requires correction. Some .Net anguages, such as F# and the Perl PDK from ActiveState do not have any drag 'n drop support at all, since they do not support the "Visual" aspect of "Visual Studio" (indeed, Perl PDK does not even support Visual Studio).
At this point, I'll tell you this: stop asking everyone around you to tell you what to do, and just make a decision. You asked people for their advice, then you argued against their advice. You obviously want someone to validate a preconceived notion of yours, and you are not happy that no one is backing hat idea.
J.Ja