David,

I'm just trying to get some clearer understandings here...

1) pointers or self-modifying code... I am not aware that VFP has support for pointers and I am keenly interested in anything you can point me to to confirm that VFP's code can, indeed, be self-modifying.

2) garbage collection... are you saying that VFP doesn't do any or are you saying that it is done better in CLR?

thanks in advance


>Many things.
>.NET code runs in a managed enviroment, the CLR which is like a virtual machine. It doesn't allow pointers or self modifying code. Garbage collection is controlled by the CLR that cleans up circular references. Code access security assures that the identity of the calling routine is really who it claims to be. Permissions can be demanded of the calling code and managed with a security policy.
>There are many, many advantages to running in a managed environment.
>
>
>>What would make a .NET Framework application be more reliable than a VFP application? And, what would make it more secure? At first, this is based on a set of minimum requirements. Without those requirements, also, how could such an affirmation be made?