Legacy C# .NET system to update

Jobs
1

We’re talking to a client who have a legacy database with web interface, built with C# and .NET

Immediate need is to do some maintenance, but looking at porting the whole thing to a different stack.

Is this in anyone’s area of expertise? I’ve mentioned the C# and .NET aspect to a couple of developers, and the response has been, “Blimey!”

2

I get the reluctance to maintain the stack, but technically C# and .NET are not actually legacy technologies even if they are in a lot of people’s minds! Not my area but there are definitely still devs who work with these

3

Yes, I gather that, thanks. It’s the client’s system that is legacy – was built about a decade ago. Hoping to be able to port it over to something that more devs in our circles use, eg Python or Ruby, getting away from Microsoft ecosystem.

4

Just a couple of comments that’ll maybe help people to decide:

  • what’s the code base size/shape, lines etc.?
  • how layered is it, if the database stuff is somewhat isolated it gets easier
  • (my opinion only) I wouldn’t move towards Ruby as a choice

Ten years isn’t that old, it could have been COBOL.

Best Hugh

2 Likes
5

I can give more details privately if any co-ops here ask me.