Ken,

This really is UNreasonable.
For one thing, I'd hazard that the high majority of (VFP) developers have barely touched much of .NET and that those who have may well have started with ASP.NET.
Another thing is that .NET keeps promising things for the near/later FUTURE. How the h*ll is someone who has minimum knowledge of .NET supposed to even know wht 'is' now and what will be sometime sooner or later???

This issue is precisely what most of us look to Microsoft to guide us on, depending on MICROSOFT's inside knowledge of future directions to LEAD US, by providing things that make good use of important factors of .NET that we, frankly, have no sensible ideas about.

As it stands now you're putting an IMPORTANT issue in the hands of a very very very FEW developers who, while they may have modest strength with .NET (and much more with VFP), also have NO idea of what's coming down the pipe or of non-obvious 'relationships' between current things (and future stuff).
I'd much rather have that limited even further to MICROSFT staff ONLY because at least MICROSOFT staff have access to insiders who do know future plans.

Finally, I'm wondering if this whole topic was actually started so that you could gauge the depth of knowledge about .NET in the VFP community at large.
If that's the case you have your answer - virtually none of us have the requisite knowledge to rspond intelligently to your request. So you might as well put it into the hands of MICROSOFT staff (VFP Team, consulting widely with .NET staffs) and deliver us something that is practical and useful for the future.

cheers


>Releasing things takes time to test, document, etc. Anything we would do like this would take way from other future efforts. Is it worth that? Also, even if it is not supported, anything we release sends a message. If it is not the best way to solve a solution in an application, do we want to be guiding people to do things the wrong way? While we are open to reconsider, we must receive well thought out scenarios which describe why someone needs the utility and how it will be used compared to other ways of solving the problem. So it is really up to the community to come up with convincing reasons it is needed versus other ways of solving similar technical needs. For things like DirecxX on a windows form, probably the best solution is to use a .NET WinForm to host/run it.