That's the other problem - none of the mags seem to pick this stuff up which doesn't help the general knowledge and discussion in this whole area. I think it goes back to what MS chooses to emphasize and that alone...
>I recently read What's New in VFP 8.0, and I was surprised how much was done in the web services area. Either it wasn't publicized as much as the other new features, or I just missed it. In any case, it is easer to both create and consume these services in VFP8. Also, there's a visual web service class and builder that you can drop on a form and create data bindings to the service. Pretty cool stuff.
>
>>ActiveVFP works fine with VFP9Beta from both ASP.NET and ASP.
>>Admitedly, I have looked forward to anything dealing with .NET interop, web services, web features, etc. and, for me, there's been pretty much nil done in this area since VFP7, which is a shame. Somebody else might feel the same way about the ReportWriter and, in that case, probably would disregard my recommendation anyway.
>>In my mind, having some basic documentation about COM interop and some examples would have been the minimum MS should have done in this regard. I might have entertained the idea of upgrading if this little bit was put in there. I also think this has serious ramifications for the future of VFP. MS is not even willing to make it clear how to work with the mainstram product, .NET. This really translates to "we really want you to convert vfp code to .NET, not interop with legacy code"...
>>>
>>>I don't have a problem with you expressing your opinion -- I just was very surprised that you had not upgraded past VFP 7, yet claimed that the VFP Team had not added much to the product.
>>>
>>>Have you downloaded and tested yet with the VFP 9 Public Beta? If so, does everything with your open source software still work OK? That's important to know since the product is still in beta and any problems you find could perhaps be resolved.