<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Exploring VB .Net from a VFP Perspective (Part II) (by John Koziol)</title><link>http://blogs.msdn.com/vsdata/archive/2005/02/15/374138.aspx</link><description>Sheesh. Some of the feedback I'm getting on this series makes me feel like a traitor to the Visual FoxPro community. Nothing could be further from the truth; I love the VFP community and I am a staunch supporter of VFP and have been for many years. I</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Exploring VB .Net from a VFP Perspective (Part II) (by John Koziol)</title><link>http://blogs.msdn.com/vsdata/archive/2005/02/15/374138.aspx#374275</link><pubDate>Wed, 16 Feb 2005 11:40:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:374275</guid><dc:creator>wOOdy</dc:creator><description>Hi John; no, of course you're not a traitor. I'm with you that VFP programmers should also have knowledge of other tools. And if that's only just for realizing how comfortable and easy the FoxPro environment is! Without the experience of how much you loose, if you switch to another development system, you cannot value the really feature-rich, stable  and proven environment of VFP.&lt;br&gt;&lt;br&gt;The main reason for the sensitivity of the FoxPro community against every mention of DotNet is the really amazing ignorance of Microsoft for their customer needs.  DotNet is a cool development system, IF you are in the midrange or enterprise level. But it's an absolute overkill for anything smaller. There are millions of customers in the small business area, which are best served with a tool like FoxPro. But as long as MS spends Millions of Dollars for DotNet only and not one Cent for VFP: what do you expect? If your needs are constantly ignored, but you get constantly reminded that DotNet is the way to go, even if it can't solve your customers needs like FoxPro could?&lt;br&gt;&lt;br&gt;</description></item><item><title>re: Exploring VB .Net from a VFP Perspective (Part II) (by John Koziol)</title><link>http://blogs.msdn.com/vsdata/archive/2005/02/15/374138.aspx#375539</link><pubDate>Thu, 17 Feb 2005 19:51:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:375539</guid><dc:creator>Kelly</dc:creator><description>Thanks, John (and yag, etc.) Stay the course. Rememeber that the majority of us love to get this kind of info and the vocal minority, well they will do their thing no matter what, right? :)</description></item><item><title>re: Exploring VB .Net from a VFP Perspective (Part II) (by John Koziol)</title><link>http://blogs.msdn.com/vsdata/archive/2005/02/15/374138.aspx#375979</link><pubDate>Fri, 18 Feb 2005 09:43:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:375979</guid><dc:creator>John Koziol</dc:creator><description>Thanks, Kelly!&lt;br&gt;&lt;br&gt;Woody, I agree with you for the most part. VFP is a great environment for small to medium size businesses.  A good VFP developer already has his framework and can put something together in short order. &lt;br&gt;&lt;br&gt;OTOH, the .Net Framework is a huge behemoth and difficult to master. &lt;br&gt;&lt;br&gt;So....I guess what I'm saying is that no one is compelling you to adopt a VS.Net language if you believe that VFP fits the needs. I am a firm believer in the right tool for the right job. &lt;br&gt;&lt;br&gt;.Net is a lynchpin in the future success of Microsoft products and enterprise development in the Windows world. There can, and will be, situations where it clearly is the best tool. The decision to learn it should be made on the basis of what best serves your clients.&lt;br&gt;&lt;br&gt;At some time in your past, you moved to VFP from something else. </description></item><item><title>re: Exploring VB .Net from a VFP Perspective (Part II) (by John Koziol)</title><link>http://blogs.msdn.com/vsdata/archive/2005/02/15/374138.aspx#385958</link><pubDate>Sat, 05 Mar 2005 21:13:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:385958</guid><dc:creator>Carl</dc:creator><description>&amp;gt;&amp;gt; At some time in your past, you moved to VFP from something else. &lt;br&gt;&lt;br&gt;Yeah, I moved from dBASE II. &amp;lt;lol&amp;gt;&lt;br&gt;&lt;br&gt;Then moved to dBASE III Plus, FoxBASE+, and then FoxPro.</description></item></channel></rss>