>Ed
>
>Thanks for the technical details- (I think) that was what I understood.
>
>So the question stands: where is the technical justification for a West Wind user to abandon it all and shift tools just to get the CLR?
>

At the moment - if you need to subclass .NET services directly, without Interop layers - is at least one time. Rick is obviously the person who ought to answer the question about the impact of IL and .NET on West-Wind; it's his puppy, not mine. I can fall back on C++, and create either managed or unmanaged code as needed, and know enough VB to know that if I have to go, I can go that way. And I'm no worse off than the rest of the crowd wrt C#; it's just another language.

If there's something compelling in .NET that simply demands that I use an IL-based product, I've got plenty of time. For now, the feature set isn't stable enough for even an early beta, so I'll play and see what I sacrifice staying with VFP like I use it now - much of my prototyping and data conversion work is done in VFP, but I end up implementing much of what I prototype in another language now, to deliver features which VFP isn't geared to deliver. If I've got data coming in which I need to digest, and mung, VFP's my first choice to do the job. if I need to deliver a free-threaded component with a small memory footprint and lots of linked list manipulation, VFP isn't a good fit.