I don't know if this has been covered here, but a search didn't reveal
a good fit. Sorry in advance and all that.
SCENARIO. Small software house used to building small, bespoke apps
using VB6, Access VBA etc.
The customer has two related products built using VB5 and VB6, which
they wish to amalgamate into a shiny new product using VB.NET FYI, it
will use a SQL Server backend, Terminal Services etc. A thin-client
thang.
Three developers have been given the task of building this. One has
about a year's experience of ASP.NET, the other two are more or less
new to .NET None has any substantial OO experience. The required
system has the same forms and logic as the old system, so there is a
good chance that business processes can be just cut and pasted from
the previous apps.
The new app will have about 70 forms and 30 reports.
HOWEVER. The software company tend to build similar products for
different clients, and think that building up a set of generic base
classes for use in all projects would be a good idea. The bible for
this would be Rockford Lhotka's 1 on 1 VB.NET Business Objects. This
would require a) one or more people to design the classes and b) the
team doing the current project to be able easily to use them. The
team doing the project are nervous about this, and would rather just
build the app in the same old way that VB always worked, since that
would mean that the maximum code could be reused from the old system,
and would do away with the learning curve and debugging problems
associated with complex OO inheritance issues etc.
Any thoughts?
TIA
Edward
--
The reading group's reading group:
http://www.bookgroup.org.uk