<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Microsoft: How does Visual FoxPro get &#8220;It Just Works&#8221; support?</title>
	<atom:link href="http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/feed" rel="self" type="application/rss+xml" />
	<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/</link>
	<description>Shedding some light on topics of software development, Visual FoxPro, saving our planet, paying it forward, and anything else I find important enough to share.</description>
	<lastBuildDate>Sun, 13 Jan 2019 18:50:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Joel</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1447</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Mon, 28 Sep 2015 17:12:15 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1447</guid>
		<description>Microsoft recently added VB6 &quot;It Just Works&quot; support for Windows 10.

https://msdn.microsoft.com/en-us/vstudio/ms788708.aspx

It would still be nice to get this level of support for VFP 9.0 runtimes.  Heck, given the changes in the last couple of years, maybe they&#039;d be agreeable to making it open source.  I won&#039;t hold my breath on either account.</description>
		<content:encoded><![CDATA[<p>Microsoft recently added VB6 &#8220;It Just Works&#8221; support for Windows 10.</p>
<p><a href="https://msdn.microsoft.com/en-us/vstudio/ms788708.aspx" rel="nofollow">https://msdn.microsoft.com/en-us/vstudio/ms788708.aspx</a></p>
<p>It would still be nice to get this level of support for VFP 9.0 runtimes.  Heck, given the changes in the last couple of years, maybe they&#8217;d be agreeable to making it open source.  I won&#8217;t hold my breath on either account.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VB6 Programming</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1432</link>
		<dc:creator>VB6 Programming</dc:creator>
		<pubDate>Fri, 08 Aug 2014 07:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1432</guid>
		<description>To get &quot;It just works&quot; support from Microsoft, I suggest ...

1) Create a call on the Microsoft UserVoice site like this one (about the VB6 programming language):-
     http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi
 and get as many votes as possible

2) Contact as many people within Microsoft as you can - by phone, email, Facebook, Twitter, etc.  - and keep contacting them.

3) Get as much publicity as you can in magazines and on websites. Such as
     http://www.i-programmer.info/news/136-open-source/7454-microsoft-refuses-to-open-source-vb6.html</description>
		<content:encoded><![CDATA[<p>To get &#8220;It just works&#8221; support from Microsoft, I suggest &#8230;</p>
<p>1) Create a call on the Microsoft UserVoice site like this one (about the VB6 programming language):-<br />
     <a href="http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi" rel="nofollow">http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi</a><br />
 and get as many votes as possible</p>
<p>2) Contact as many people within Microsoft as you can &#8211; by phone, email, Facebook, Twitter, etc.  &#8211; and keep contacting them.</p>
<p>3) Get as much publicity as you can in magazines and on websites. Such as<br />
     <a href="http://www.i-programmer.info/news/136-open-source/7454-microsoft-refuses-to-open-source-vb6.html" rel="nofollow">http://www.i-programmer.info/news/136-open-source/7454-microsoft-refuses-to-open-source-vb6.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1414</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Thu, 18 Jul 2013 15:54:30 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1414</guid>
		<description>Extended runtime support would be extremely beneficial, if only for giving peace of mind to people who are relying on FoxPro right now.  At my company, we have a Visual FoxPro 9 database system with about 200K lines of code, with hundreds of tables and hundreds of report forms.  The system is absolutely critical to the operation of the business.  The concern is that a new version or new upgrade to an existing version of Windows will be incompatible with VFP 9, and then what do we do?  We have been slowly moving data out of FoxPro into Postgres, which generally gives an immediate performance boost and we think should be easier to work with in the event we have to change the front end to .NET or something else.  My hope is that one of the projects floating around, such as PolarFox, will give us a supported upgrade path while allowing us to use our current code, but I don&#039;t know how realistic that is.

What is the thinking among developers now? Is there a belief that the installed base of VFP is still too big for Microsoft to release (within the next 10 or so years) a version of Windows that is incompatible with VFP?</description>
		<content:encoded><![CDATA[<p>Extended runtime support would be extremely beneficial, if only for giving peace of mind to people who are relying on FoxPro right now.  At my company, we have a Visual FoxPro 9 database system with about 200K lines of code, with hundreds of tables and hundreds of report forms.  The system is absolutely critical to the operation of the business.  The concern is that a new version or new upgrade to an existing version of Windows will be incompatible with VFP 9, and then what do we do?  We have been slowly moving data out of FoxPro into Postgres, which generally gives an immediate performance boost and we think should be easier to work with in the event we have to change the front end to .NET or something else.  My hope is that one of the projects floating around, such as PolarFox, will give us a supported upgrade path while allowing us to use our current code, but I don&#8217;t know how realistic that is.</p>
<p>What is the thinking among developers now? Is there a belief that the installed base of VFP is still too big for Microsoft to release (within the next 10 or so years) a version of Windows that is incompatible with VFP?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Byron</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1411</link>
		<dc:creator>Byron</dc:creator>
		<pubDate>Sun, 26 May 2013 16:14:31 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1411</guid>
		<description>I forgot to say it was Excel 360</description>
		<content:encoded><![CDATA[<p>I forgot to say it was Excel 360</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Byron</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1410</link>
		<dc:creator>Byron</dc:creator>
		<pubDate>Sun, 26 May 2013 16:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1410</guid>
		<description>I thought all was working well until I tried an ADO routine that works well on Windows 7 to import the xlsx format file and the ADO.connect does not connect.

Has anyone else seen this?</description>
		<content:encoded><![CDATA[<p>I thought all was working well until I tried an ADO routine that works well on Windows 7 to import the xlsx format file and the ADO.connect does not connect.</p>
<p>Has anyone else seen this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John F</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1405</link>
		<dc:creator>John F</dc:creator>
		<pubDate>Fri, 03 May 2013 16:43:07 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1405</guid>
		<description>I&#039;m finding it running massively faster than on Windows 7 - there are no more of the memory issues
I use it every day for maintaining massive amounts of data and the Rushmore Optimisation is important to allow me to number crunch at high speed
I don&#039;t know what happened to the OS architecture between Windows 7 and Windows 8 - I don&#039;t care - I just works</description>
		<content:encoded><![CDATA[<p>I&#8217;m finding it running massively faster than on Windows 7 &#8211; there are no more of the memory issues<br />
I use it every day for maintaining massive amounts of data and the Rushmore Optimisation is important to allow me to number crunch at high speed<br />
I don&#8217;t know what happened to the OS architecture between Windows 7 and Windows 8 &#8211; I don&#8217;t care &#8211; I just works</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1394</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 24 Sep 2012 11:01:35 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1394</guid>
		<description>visual foxpro is very very good language tool for us
please upgrade it upto computer life or upto life of sun &amp; earth</description>
		<content:encoded><![CDATA[<p>visual foxpro is very very good language tool for us<br />
please upgrade it upto computer life or upto life of sun &amp; earth</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mick</title>
		<link>http://rickschummer.com/blog2/2012/06/microsoft-how-does-visual-foxpro-get-it-just-works-support/comment-page-1/#comment-1366</link>
		<dc:creator>Mick</dc:creator>
		<pubDate>Tue, 05 Jun 2012 16:56:59 +0000</pubDate>
		<guid isPermaLink="false">http://rickschummer.com/blog2/?p=1329#comment-1366</guid>
		<description>Yeah, sitting in a &quot;pocket&quot; grinding out VFP code very day (and some C# and PowerShell too.)  Wouldn&#039;t be against seeing the &quot;It Just Works&quot; label under the Fox Head pennant, but if not What the Funk, still works :)</description>
		<content:encoded><![CDATA[<p>Yeah, sitting in a &#8220;pocket&#8221; grinding out VFP code very day (and some C# and PowerShell too.)  Wouldn&#8217;t be against seeing the &#8220;It Just Works&#8221; label under the Fox Head pennant, but if not What the Funk, still works <img src='http://rickschummer.com/blog2/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
