Over the 12+ years in this space I gained a lot of experience in developing client and client/server applications, database design and developent and office automation.
Should you migrate to .NET?
That's a tough question. There is a lot of Visual Basic code out there, and if aint broke, why fix it? The problem is that most developers these days perfer to develop using the latest cool tools out of Microsoft, often leaving companies with a problem.If you don't want to migrate and just need to some updates to suit new business processes, then why not contact me and we can talk through your needs and see what is the best way forward for you.
I develop code in both legacy and modern .NET toolsets, and am quite happy at maintaining/supporting your VB software as required. If on the other hand you want to upgrade and migrate to .NET, then I can interpret your VB code base into modern .NET code.
In general I develop using C#. I really do not like the VB.NET that replaced Visual Basic, with syntax changes, keyword changes and lots of Visual Basic code just not supported any more. So, any .NET development I do is in C# and VB is only used for legacy Visual Basic work.
The other reason for using C# is that a lot of developers were of the same as opinion as myself, and a lot more are available for hire for future work moving forward.
But our software is client/server and we need it to be more distributed..
No problem, I've have developed enterprise application for companies such as the Halifax and Jarvis Facilities in the UK and Bankwest, Public Transport Authority and others in Australia. This development has been in all layers, from client and kiosk applications, to middle-ware, to back-end database development (mainly T-SQL) and most things in between.So, if you think I can help then why not get in touch?
