Conversion time from COM to .NET Web Service
I'd give a *very* rough estimate of 75%, based on my early experiences. This
is based on the time it would take to re-write my components *in the same
language* as they are now and how much time it would take to *re-think* what
each component does and how it might be done better in DOTNET.
The problem with getting a more specific number comes from a couple of
things:
1. A "good", reusable component takes a *long* time to write, tweak,
enhance, debug, etc. So, does the base number include the full year it took
to write, or the actual time if you had to re-write it from scratch in the
same language?
2. For many objects, a simple port to DOTNET will take only a short time, if
you're familiar with DOTNET. More importantly, your old components should
probably be re-thought out to take advantage of new coding styles of DOTNET.
Meaning, don't just translate ADODB.Recordset into ADODataSet, but maybe you
don't want your object to a Recordset/DataSet - maybe it returns an XML
string. Then your calling components must now load the XML string instead of
using a Recordset, etc. etc.
It's a different mindset than previous versions of VB and not just in the
language.
-Pickle
Quote:
> Hi,
> I'd like to know from your own experience approximately how much time it
> takes to port an existing COM component into a .NET Web Service, as a
> percentage of the time it took to build the COM component.
> For example, if it took 4 weeks to build the COM component, and 1 week to
> port it to a .NET Web Service, then that would be 25%.
> If there's any white-paper from Microsoft or anyone else about this, I'd
> really like to have a link to that.
> Thanks!
> --
> Cheers!
> Scott A. Keen
