Moving to VB.NET from VB6

[sevenhalo]

I've seen you mention "reverse engineering .net" about three times now.

All I have to say is "web services." If you're not going to obfuscate it, and you're on a LAN anyway; set up a service that houses all of that critical functionality and have users subscribe.

---IMO---
If you don't want to upgrade, then be honest with your boss and say just that. If he/she asks why, just say that it's a training issue or flat out tell him/her it's just not in your best interests. If you haven't used the Fx first-hand, don't rely on a bunch of strategically picked articles to develop an opinion.

If .Net was as insecure and unsafe as your facts sheet make it sound, how come we haven't heard of any company getting nailed with an exploit that set them back millions of dollars? Or even identity theft (not directly relating to hardware theft or user misconfigurations).

Since the the Fx came out half a decade ago; the only negative articles are a bunch of pestimistic, nostradamus-like predictions. A wise man once said, "Don't dog it till you try it."

[esposito]

If .Net was as insecure and unsafe as your facts sheet make it sound, how come we haven't heard of any company getting nailed with an exploit that set them back millions of dollars? Or even identity theft (not directly relating to hardware theft or user misconfigurations).

Since the the Fx came out half a decade ago; the only negative articles are a bunch of pestimistic, nostradamus-like predictions. A wise man once said, "Don't dog it till you try it."

Paraphrasing the article I mentioned above, I could say, "If .Net were secure and safe, MS would not be missing a billion dollars of upgrade revenue three years after the launch of VB .NET since VB6 users aren’t upgrading to VB .NET at all."

[sevenhalo]

Paraphrasing the article I mentioned above, I could say, "If .Net were secure and safe, MS would not be missing a billion dollars of upgrade revenue three years after the launch of VB .NET since VB6 users aren’t upgrading to VB .NET at all."

And aren't you the poster boy for this? Literally, asking people for reasons not to upgrade instead of researching .Net yourself?

I agree not all projects need to be updated, but alot can benefit. I'm only upgrading projects that I can incorporate into new development. For instance, if I'm building an internal purchasing system and our inventory system is in VB6; I'll upgrade the inventory system and make some changes along the way to optimize them for eachother.

I'm by no means prancing and skipping through the server room with high power magnents "ridding the company of evil legacy code." I just start all new development with the "what other projects can I incorporate?" question in the back of my mind.