Quote: "Lol yeah ok, not drag and drop really, at least not to that extent although it is an extremely visually based IDE. Just was trying to make a point."
Point taken - thank you for clarifying. Yes .NET has added some nice time saving features like dropping sqlDB connection objects, datasets, crystal reports objects on a tray and quickly configuring them. The thing is you don't have to use anything graphical if you choose not to - build your entire app from code - I use the best of both worlds.
Quote: "However, the fact would remain, you are, say an applications developer? Probably a successful and experienced one."
I code professionally - I hold my own.
Quote: "But what can you develop on an OS other than Windows? You'd need to learn an entirely new language/API, no?"
Yes, but what does that mean? Just because I am a huge advocate of vb.net as compared to vb6, what does that have to with anything else I may or may not know? If I were a neurosurgeon, would you then criticise me for not knowing the in's and out's of pediatry??
Quote: "Doesn't that make VB.NET & C# it a bit, kinda, toytown? At least with C++.NET you can choose to program in managed code or not (obviously not if you want it portable in any way)"
If "toytown" refers to managed code, you're missing the boat. For all the daunting tasks that coding for business applications brings, adding powerful tools to your kit like managed code Garbage Collection, as one example, to free the developer of object memory issues - I say bring on the TOYS!!
Quote: "For example ASP.NET makes it seem as though you are programming for windows (in a crude sortof way). What do you have to know about how the web works to do that?"
Again, I think you are assuming that .net developers need to know nothing - simply wrong. Just because the toolbox has a host of shiny new toys to play with, the knowledge level has gone up, not down. I am sad that people have the misconception the .net is "dumbed-down", quite the contrary, we vb guys have been elevated to the level of the "snotty C++ developers" of days past (and I say that in the warmest regard)Do you know anything about ASP.NET or .NET Remoting via HTTP/SOAP/XML or WebServices? If you did, we wouldn't really be having this conversation, sorry to say.
Quote: "Didn't it hurt even a little to throw out all your own objects, code and experience in favour of MS code that does it for you and ties you to their OS? And then (possibly) reduces your wages?"
Again, you show how little you really know about .net and how it works. I didn't have to throw away anything that I didn't want to - It's called COM-Interop. Objects that I wrote in COM can be referenced in any .net assembly, where they get wrapped with an Interop dll and away you go - complete interoperability. This holds true for all previous ms Com objects and ocx's. I will admit I use very little from the vb6 days in my .net projects but that is by choice, not because we were forced. I choose to drive the .NET Ferrari, but it is perfectly fine if someone wants to still take out the vb6 280zx once in a while. Whatever suits them but I only ask that all is researched and conclusions are made based on ALL the facts, no preconceived notions, or facts from a history dead and gone. Oh, and since having added .NET to my resume I have increased my market value roughly 20-35%. It's the "hot item" in the business world these days - it's a nice time to jump in, especially if your a vb6 guy, now's the time imho. Let's see, ease of use, unseen power and flexability, shorter dev cycles, and more money - for less headache - you decide.
(And remember this is all just MHO, coming from the point of view of a VB6 coder)
-RUST-
