Venelina,

The possibility of a VFP .Net has been discussed in many threads here on the UT. I'll let Ken give you a more official response, but IMO, VFP .Net would not be good. It would pretty much look like VB .Net and you wouldn't gain anything from it.

As for creating OCX controls in VB .Net, you won't ever get that capability. OCX is COM and COM goes away under .Net.

>Hi,
>I work in software firm, which is Microsoft® Certified Partner (ID# 562791).
>We develop applications primary on VFP 6.0/7.0. Because in VFP we cannot develop ActiveX® controls (and we often need to develop controls with specific functions), we develop them using VB6.0. This is done primary by me.
>As a partner, we receive .NET Studio Beta 2. An unpleasant surprise in this release for us was missing VFP.NET. When I read some articles in UT I understood that it will not be included in first release of VS.NET. My first question is:
>1. When we could expect VFP.NET release in .NET Studio?
>Further, until we receive VFP.NET, we are trying to develop some controls in VB.NET. This is necessary, because in .NET some form controls have functions, which we need to develop our VFP7.0 applications. For example, in VB6.0 TreeView control doesn’t have MouseWheel event, but in .NET TreeView form control has this event. My next question is:
> 2. Can we expect possibility to develop .OCX controls (not .DLL) in VB.NET at all?
>In the meantime we are trying to develop VB.NET class, which encapsulates TreeView form control functionality and instantiate this class in VB6.0/VFP7.0. With this we met following problems:
>- Our class inherits TreeView form control class. In spite of this, while we do not define public interface of class, all properties, methods and events are invisible in VB6.0/VFP7.0, even if class is registered for COM interop.
>- Defining public interface solve this problem partially: properties and methods work with VFP7.0 (with SP1), but events are exported in COM type library as two methods (add_ and remove_). Therefore, EVENTHANDER() function in VFP7.0 fails to bind instantiated object with user defined class, developed to handle these events.
>- I generally fail to implement this class in VB6.0. The class is split into three parts:
>o <1> the control class itself;
>o <2> the class, which encapsulates interface members;
>o <3> another (xxxEventHandler) class (we built test class with one event).
>I was unable to bind instantiated control from control class with interface members in another class. More than, I have no idea in which manner can I handle the events.
>- In order to use VB.NET class to instantiate in VFP7.0/VB6.0 control with user interface (visible control, which will respond to user interactions), which is the best way to develop class in VB.NET: as Class library or as Windows control library. In difference of VB6.0, both these projects are currently compiled into .DLL file.
>
>Could you help us with any ideas or suggestions.
>Thanks in advance:
>
>Plamen J. Ivanov, MCP# 2361156
>VB team leader