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 from 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.