Over the past 3 years I've dabbled (I say dabbled because I can never spend enough time on it to really know it) in c#. Now I am switching to vb.net.. One thing I have learned though, while I thought there were a hundred ways to 'skin a cat' as they say in VFP, there are a thousand in .net!



>EXCELLENT SUGGESTION Tracy,
>
>I know I'll be looking into what others post for samples, and your right about the basics... If a person doesn't utilize a full-blown framework that takes care of all the business rules, hiding methods for handing back-and-forth, and the other thousands of classes within .net, it can be very intimidating for others just trying to get a mental map on the process.
>
>
>
>>Ok, we've had this discussion numerous times. The majority seem to decide that there are sufficient examples out there (on MSFT or the web or even installed solution examples) of simple, data handling apps from the ground up in vanilla VFP and dotnet. In the past the discussion were more centered around comparisons as to the capabilities of each and that there are just 'too many ways to accomplish it' to decide on what method to use in the examples.
>>
>>Given that the UT community is so fortunate to have knowledgable VFP developers now in the NET community, is anyone willing to do this now?
>>
>>Not a competition. Not a best practices scenario either. Granted, depending on too many variables, a different method using each tool may be required.
>>
>>Please, base the dotnet examples on a simple vanilla VFP example (for those VFPers who have not had the time or money or opportunity to get started on dotnet yet - it really doesn't matter WHY) using vanilla vb.net or c#.net. No 3rd party tools, frameworks, or add-ons.
>>
>>For everyone comfortable with dotnet, please CONSIDER volunteering some time and effort into creating a simple data handling app in vb.net or c# based on a simple vfp data handling app.
>>
>>Ideally all 3 examples (VFP, C#, and VB) would be available for download here on the UT.
>>
>>Help your fellow peers.
>>
>>No competition.
>>
>>NO ARGUMENTS on WHY DID YOU DO IT THAT WAY or I WOULD HAVE DONE IT DIFFERENTLY or THIS ONE IS FASTER OR MORE EFFICIENT. Just EXAMPLES of simple data handling that gets the job done.
>>
>>Doesn't have to be ideal or the best way to do it.
>>
>>Using SQL Server 2000 or 2005 backend (let's make it a common business layout - no arguments on using mysql or anything - just kiss - and everyone can install SQLServer 2005 Express if they don't have it already).
>>
>>Any takers? :o)