convincing ignorant it managers

  • Thread starter Thread starter VBCodr
  • Start date Start date
V

VBCodr

Please don't nail me if this is the wrong forum - please
direct me to the right one.

I have been tech lead/architect on a very big asp/com+/vb6
internal app. I am trying to convince the powers that be
to allow us to move to vb.net, but the only mantra they
know is "don't fix what ain't broke."

There is no way we could do a port - the system is just
way too darn big. I'd like to begin developing the new
stuff in vb.net and slowly shed vb6, but I need help in
the convincing.

They would need to buy vs.net, and who knows what other
expenses there would be, so it's been a very tough climb.

any help?
 
What is wrong with "if it aint broke don't fix it"?

The COM+ framework has no direct translation in DotNet you have to monkey
with the interop layer in order to get your dotNet components to run under
COM+. Given my current experience, using Office via the Interop layer, I
would stay away from it if at all possible for performance and flakeyness
reasons.

The only real benefit in recoding your project is with the ASP to ASP.NET
conversion. The ASP.NET model is much more flexible and readable. It is
much easier to separate business logic from the presentation layer given the
code behind features of ASP.NET

If your app is undergoing many mods' you might consider the upgrade but be
prepared for a redesign at the same time since the models and frameworks are
vastly different, and certainly do not count on the "Upgrade Wizard"

Dan
 
* "VBCodr said:
Please don't nail me if this is the wrong forum - please
direct me to the right one.

I have been tech lead/architect on a very big asp/com+/vb6
internal app. I am trying to convince the powers that be
to allow us to move to vb.net, but the only mantra they
know is "don't fix what ain't broke."
Click to expand...

The main question is: "Why move to .NET?". Does .NET habe any
advantages? No, if the current system works without problems. "Never
change a running system" saves money.
There is no way we could do a port - the system is just
way too darn big. I'd like to begin developing the new
stuff in vb.net and slowly shed vb6, but I need help in
the convincing.
Click to expand...

Why convince? If there were any big advantages, you won't need to
convince people.
 
Hi VBCodr

"don't fix what ain't broke."

True

However, some things need maintenance and that means that the economic
lifecycle ends as soon as the maintenance to keep it up is more expensive
than building and using new.

An other example is about the sailing boat companies, those who did sell
transport are still there and the others are history.

I do not know if this is in your case the same, but maybe you can use this?

Cor
 
VBCodr,

I convinced my management to move a bunch of apps from Access to .NET by
giving them examples of upgrades they'd requested that wouldn't be feasible
(or very difficult) in Access. In my case, those features were built-in
graphical GIS, advanced user interface (configurable, multi-window,
multi-pane), and lots of built-in graphing and statistical analysis.

I think you're going to argue for a platform move, you should probably
be prepared to tell them what features will be better implemented in the new
platform!

Erik
 
VBCodr said:
This has all been very useful.
Thanks!
Click to expand...

In my experience we have seen dramatic improvements in performance
with ASP.NET over ASP.
This give a lot more room to grow with a web project.

HTH
 
I think my problem is one of perception. Some of the
replies here follow my manager's same agruments - if it
ain't broke.....

but that's not what I'm talking about. I have no
intention of doing a full blown port to .net. I agree
that it works fine, no performance issues, no UI issues,
etc. What I am trying to convince him of is the need for
NEW development to be done in .net.

Specifically, we have a project coming up that I
estimated to be 6-8 months (awaiting final spec). I
think we could do it in about the same time with .net,
including the ramp up time needed to get used to a new
dev system.

The project is essentially a web service that will serve
financial and investment information to our new business
partner, who has a public site for their clients. It is
my contention that the service, and the other
requirements, offer the perfect opportunity to move to
the new platform. THEN, as we have time, and updates are
needed for the existing code, we could slowly port piece
by piece.
 
Back
Top