Hi Geoff,

If I understand you correctly you plan to extend your applications by just
adding new layers around it in C#.
I can see lot's of situations where that is applicable but what about the
situations where you have to change the business logic within your VO code?
The moment you have to change that you will have to dive into your VO code
and change that. That means AFAICS that you are still in need of the most
bug-fixed VO version around... And that will be VO 2.8, even if you don't
like the fact that some or all of the problems in VO, you think are
important, are fixed...

The second problem I see with your approach is that you will not be able to
bring the beaty of .NET within your VO code. You said you have written your
own XML Parser (as we did). Wouldn't it be nice if that can could be
replaced by the .NET version. That one supports all the new XML-stuff like
XSLT 2.0, Schema's, etc... Leaving all your code in VO makes it more
difficult to bring that code into the future...

Patrick.

Mostly. But a lot of the human interface is turning into remote access -
ASP.net is becoming more important than I expected. A lot of other
communications aspects are being solved with web services and right now,
that means C#. Equally for MS Office integration code.

You are correct. If this is required then it will probably be modified
in VO but we find this does not happen often. Most of the calculation
code we wrote 3 years is still in use unmodified. The calcs work and
only the data layer has changed. New calcs can be written in whatever
language at the time.