Thanks Steve

I guessed that would be the case, since I have never seen one of our VB guys use a bought in framework.

I have no intention of moving from VFP for my large scale projects unless I am forced into it. However I have decided that it is wise for me to pick up a CLR language as well just to be on the safe side and to get the VB programmers off my back in work. (They can get a bit snotty when they see the speed at which we can turn in applications in VFP, I can do in a few days work they quote months for). No matter how often I demonstrate how effective VFP is they always manage to convince management that VFP is dying.

I am hoping that VFP can demonstrate a strong connection to .Net even without being part of the CLR. How this can be achieved I have no idea.

Are you looking at any CLR languages yourself?


>A bit too soon, you could say that. Considering that no VB framework has emerged in over a decase of VB, I wouldn't hold my breath. Especially considering that there's no built-in metadata handling like we enjoy in VFP.
>
>Dot Net *is* a framework. It's been developed by people with no (zero) successful framework experience. Good luck :-)
>
>**--** Steve
>
>>If I move to a .net language I plan to learn from my experience with VFP
>>and hit the ground running with a well written development framework like Visual Maxframe or Codemine.
>>
>>Does anyone know if there is such a product on the market yet?
>>Or is it a bit too soon.