Were using .net 1.1 and sqlserver 2000, mm.net and infragistics. We are planning things carefully with Kevin McNeish's help so that the transition to Whidbey won't hurt us...


>John,
>
>Just curious with .net 2.0 and VS 2005 et all what are you using for the rewrite.
>
>I'm going straight J2EE 5.0 Eclipse, Hibernate, mySQL / Oracle / SQL-server knowing full well if I keep the code very generic. I can use the MS Convert wizard to convert me to C# if J2EE dies ;)
>
>jp
>
>
>
>>Nope. We are in the middle of an extensive rewrite in .net of 5 of our premier applications. Were talking millions of lines of code, I'll let you know how the rewrite went in about 1 year from now..
>>
>>
>>
>>>Then I would say a lot of this conversion talk is wishful thinking, especially if you're not footing the bill..
>>>>I will keep my eyes open. But I do think it's a little early.
>>>>
>>>>>As I asked Martin, can you give some examples of successful complete rewrites of VFP apps to .NET or is it too early?
>>>>>>As Martin mentioned, it is just not that easy to make use of legacy code in a new app. I've worked on several apps that were developed several years and have many hands in it since.
>>>>>>
>>>>>>Typically in this case, the rewrite is used as an excuse to take a patchwork app and rewrite it f
>>
>>rom the ground up. So interop is not an option since the objective is to remove the spaghetti code.
>>>>>>
>>>>>>PF
>>>>>>
>>>>>>>That is probably one of the more insightful takes on this whole issue I have heard.
>>>>>>>
>>>>>>>>It appears most .Net apps are either new apps, or rewrites. From my experience, when companies switch from Foxpro to .Net, they are not interested in interop.