>>Well, I don't know how hard you've tried, but I would definitely try to >>convince the client that COBOL.NET is the way to go. It will allow you to >>port to a 'real' .NET language in less time and - which is usually >>important to clients - less money. Research this solution a little, I'm >>pretty sure you can shave at least $100K off the Java proposition.
Yeah, but COBOL is not going to impress anyone. No one wants it. How I can suggest that a company build their future around COBOL? Also, what isn't supported in the COBOL for .Net. Is inline SQL supported? If not, that more of an issue than my problem with the data structures. If I can port 90% or more of the code to .Net, is that better or worse than COBOL not supporting inline SQL. I'm sure the COBOL solutions has issues that it cannot support at well. >>Java old, .NET new, looky! we smarter and cheaper - I think these are very >>important messages to convey to the client. Yeah, but you know what they are going to say.... Why can't we handle data structures? So in their mind, who's smarter? If COBOL can handle it, why not C# and VB? In the end, it's all just MS ilCode. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
