What a recommendation- convert to dotNET because that's what organizations who screwed up are doing!
Are you sure that's what you meant to say? ;-)

No. And I'm fairly certain you know that. As Lacey Underall said to Danny Noonan in Caddyshack..."Nice try" <vbg>


The topic already assumed focus on companies looking to move to .NET. The question was whether the company wanted to make a complete move to .NET, or a phrased approach that retained some portion of Fox code.

I've heard a few companies talk of retaining some of the Fox code base, because they're able to effectively do so (they were writing COM components to begin with). They still want to move to .NET - in a phased approach. This probably represents the minority of all fox apps out there.

Most that I've seen or heard about are doing a total re-write, often by creating two development teams (one for the new version and a legacy team for the current version).

As I said in my last post, interop is not viewed as a magic bullet by some .NET authors who have described the performance costs of interop with the COM subsystem, as well as the possible additional efforts in managing a mixed environment. I'm not saying interop isn't an option, it is: but it does carry some considerations.

Kevin