nope, it's impossible to answer because the decision to migrate, as I keep telling people, should be based oin the relative value to the business, not on purely technological issues. Sure, .NET is 'better' from a developer's standpoint, but does the migration
offer compelling improvements and a decent return on investment? that would depend on exactly the app we're talking about, what sort of business we're dealing with, the time it'd take to perform the migration, security requirements, time that could be saved
adding enhancements, extra cost (if any) of retraining staff, whether upgrades of client or server software may be required and a myriad of other issues. As I always say, a migration has to offer a positive return on investment. If the migration costs $5000,
then the business has to recoup that amount or more solely as a result of the migration if you want to take the narrow view, sure go ahead and answer it, but you'll be missing a lot of factors. And abandoning a curent platform in favour of VB for NEW projects
is of course a different Kettle of Fish entirely. Here there are less issues with the costs of migration but there's still possible retraining, upgrading to VS.NET if you haven't already, time to install .NET on development machines and extra time in keeping
it all nicely patched and secure. Some of these factors won't matter a stuf, others will, depends on the business. it's NOT a concrete question.
RTFM - straight talk for web developers. Unmoderated, uncensored, occasionally unreadable
Atrax
All-Star
18705 Points
3733 Posts
Re: .NET versus 'legacy' apps (even VB6)
Sep 16, 2003 04:11 AM|LINK
Jason Brown - MVP, IIS