I'm not targeting the .NET framework but am answering the survey despite it saying "for net developers" because I'm a repwhore and want my points anyway.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
our main app is still in vb6; sigh. Somehow it has been configured to point to all the frameworks including 4.0 Someday soon, when the dinasour developers become extinct/retire, we may then bring it up to date.
here there are still vb6 applications.. and its kinda hard to debug and maintain it..
believe me VB6 is quite a simple langauge.. however i am agree to your point of "not a OOPS based coding", however you can mimic that!.
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow Never mind - my own stupidity is the source of every "problem" - Mixture
I usually target 4.0, as it is now widely available enough that I don't have to worry about whether users have the correct version or not.
I did one recent project using some of the new Task features, which did require 4.5. However, given that, when I ran it on a machine that didn't have 4.5, it popped up a message with a direct link to download 4.5 from Microsoft, I see no reason not to just go with 4.5 for all new projects (unless Windows XP support is still needed - but I thankfully don't need to worry about that anymore!)
Up until this last year all of my targets have been 2.0 or 3.5. Primarily for OS support and political reasons. All but 1 or 2 projects at my fulltime job and freelance work require XP support. I have 1 app that actually has to support Win2k. So 2.0 is only option.. Politics...
we constantly fight that balance of support vs convenience. Simply recompiling projects from 2.0/3.5 to 4.0 to stay relatively current may seem like a great idea for consistency and testing in department meetings.. But deploying out your app to 200+ customers and you find than all but a handful are XP users and either have to sit thru a Framework Install & Reboot or can't run your product at all because you changed frameworks can be inefficient and chaos.