I guess what I was thinking of had more to do with VFP's weak typing more than anything. I can literally type anything I want in the VFP command window and something will happen, whether it's on a data store (DBF/cursor/RDBMS) or in memory. VS.NET's just doesn't do that. I'll have to dig up some particulars if you're interested.


>Hi, Steve-
>
>I was curious about one of your comments and wanted to follow up with a question...
>
>>The VS.NET IDE is nice, but there's no command window - everything must be compiled from source into IL (Intermediate Language) before it will run - so testing certain things like you would in VFP can't happen.
>
>There is, actually, a command window in the VS.NET IDE, though at times it seems a poor cousin to the FoxPro command window. Can you give me an example of something you can test in VFP that you can't test in VS.NET? So far I haven't found anything I can't test, even if I can't test it the same way I would in the FoxPro IDE.
>
>TIA.