I think a pure .net topic is okay at a vfp conference if it addresses performing tasks in .net from a vfp point of view. For example, alternatives in a .net app that can be used as replacements for an application object found in a vfp app.

I don't think this type of session would find many attendees at a Visual Studio devcon.

pf

>>I think it's good to present purely .NET topics for a few breakout sessions, but, the focus should be on developing with VFP if it is indeed a vfp conference. Sometimes I get the impression that Ken, Rick and some of the others are using the old "bait and hook" ploy to push their new .NEt baby. I think, for a vfp conference, the focus of most sessions dealing with .NET should be using it to full advantage with VFP not as a replacement.
>
>One thing you have to remember is that we speakers don't pick the final sessions we actually do. I generally submit 10 topics to present on and then the organizers pick from that list. For SWFox I only submitted 2 .NET related topics and one of them got picked.
>
>I don't agree with you either way - whehter you like it or not, people are interested in .NET topics be it for interop or whether it's for comparing how things work in .NET compared to VFP. I can tell you too that on my Web site the most popular content is the various Interop content I have online. So not offering that content means you're doing developers a disfavor. You always have choices - there are many tracks to choose from simultaneously. Let others make that choice for themselves...
>
>I do agree that pure .NET content is not a good choice - the content should in great part relate to Visual FoxPro otherwise it's misplaced at a Fox conference...
>
>+++ Rick ---