justify .net

  • Thread starter Thread starter bill joyce
  • Start date Start date
B

bill joyce

Hello,
We have been told to stop using .net. I would like some help in
justifying .net use. I have already been there with dll hell, a better
vb. If you have been there any input will help.

Thanks
 
Need more info. Who told you to stop using .net and why (reasons.) If you
want to use MS IDEs and languages, .net is the way. Maybe they changed (or
will change) to another tool manufacturer.
 
I believe it is two reasons.

1. They do not know anything about it

2. Cost

3. the they is senior IT management
 
In many instances, writing in .NET is going to be a lot cheaper. I'm not
sure what cost they are focusing on, but there are a lot of benefits.
There's a ton of free information and resources. the IDE is very powerful
and debugging is great. You can build very impressive applications quickly.
Two of us put up a pretty advanced web stie for document tracking and
viewing in about three weeks. We really only had on developer on it and it
was his first ASP.NET app.

If they don't know anything about it, they can't know it's too expensive or
whatever their issue is. It's true that good .NET programmers aren't cheap,
but good programmers usally aren't in any language.

HTH,

Bill
 
I am not a vb programmer (used to be), and have heard growns from vb6
programmers when they look at vb.net - which I can't really speak to.
However, the upgrade path and the future TCO would seem to be something I
would tend to focus on. What is the upgrade and support path for vb6? IMO,
c# and .net is a sweet environment and very powerful. Having access to the
..net framework and remoting/web services alone could be worth it. How many
stations would you need to upgrade?
 
Is the choice between VB6 and VB.Net? And you already have Visual Studio
..Net installed?

Two obvious benefits of VB.Net (from a manager's perspective) would be
strict type checking (with Option Strict on) and structured exception
handling. The first prevents many coding errors, the later gives you better
control over those that do crop up. The end result is more robust code.

There are some disadvantages to .Net too, of course -- it requires the .Net
framework to be installed on client machines, and it's not a direct upgrade
from VB6, so it's not a good choice for upgrading or maintaining existing
VB6 code.

Without knowing more about your company's situation, it's hard to be
specific about how, or whether, VB.Net is better for you.
 
Microsoft will stop supporting VB6 in a few years. What will they do
then? Is it wise to wait until the last minute, then convert
everything over?
 
Back
Top