Hi all,

Currently we use VB6, SQL Server 7 and ASP and I need to convince 'the powers that be' 
that our future developments should be in .NET. Please note that there's no question 
of going to Java and it's a given that we will go to .NET, the issue is when we will 
make the change.

I've been asked to write a BRIEF couple of pages explaining why we should change now 
(prior to launching into some major development) and I've decided to tackle it in 2 
parts.

1) What's wrong with our current technology:
VB6 is limited to STA (KB Q291837) and does not support object pooling in MTS/COM+
ASP is interpreted
SQL 7 has no native support for XML (we are intending to make quite heavy use of XML)
MS is not focused on these technologies so bug-fixes will become fewer and less often.

2) What's right about .NET:
Framework provides huge catalogue of ready-made objects
Support for web services/XML throughout product range
ASP.NET is compiled and provides better separation of display and business logic
Choice of languages
VS.NET is a more productive and better integrated environment

Can anyone add anything suitably 'high-level' to this list or point me in the 
direction of any suitable resources (I did a search on the list archives and was 
surprised not to come up with anything).

Many thanks,

Phil Ruelle


Website: http://www.mourant.com

The information in this email is confidential. The contents may not be disclosed
or used by anyone other than the addressee. If you are not the intended
recipient, please notify us immediately at the above E-mail address or
telephone +44 1534 609000

We cannot accept any responsibility for the accuracy or completeness of this
message as it has been transmitted over a public network. If you suspect that
the message may have been intercepted or amended, please call the sender.

If this message includes attachments, please ensure they are opened within
the relevant application to ensure full receipt.
If you experience difficulties, please refer back to the sender.

You can read messages from the DOTNET archive, unsubscribe from DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to