<?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: Migrating VB6 applications</title>
	<atom:link href="http://blog.gurock.com/postings/migrating-vb6-applications/311/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gurock.com/postings/migrating-vb6-applications/311/</link>
	<description>Our products, programming &#38; business.</description>
	<lastBuildDate>Wed, 18 Jan 2012 21:41:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Dennis Gurock</title>
		<link>http://blog.gurock.com/postings/migrating-vb6-applications/311/comment-page-1/#comment-20853</link>
		<dc:creator>Dennis Gurock</dc:creator>
		<pubDate>Fri, 30 May 2008 07:33:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/?p=311#comment-20853</guid>
		<description>Thanks for the detailed comment Francesco. I really like the open and transparent approach you are taking and I&#039;m sure that prospective users will reward it.</description>
		<content:encoded><![CDATA[<p>Thanks for the detailed comment Francesco. I really like the open and transparent approach you are taking and I&#8217;m sure that prospective users will reward it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francesco Balena</title>
		<link>http://blog.gurock.com/postings/migrating-vb6-applications/311/comment-page-1/#comment-20831</link>
		<dc:creator>Francesco Balena</dc:creator>
		<pubDate>Thu, 29 May 2008 07:54:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gurock.com/?p=311#comment-20831</guid>
		<description>Thank you for mentioning our tool, Dennis.

Let me add just one thought. Code conversion tools, especially VB6-to-VB.NET tools, suffer from a bad reputation of not being enough powerful or cost-effective. To counter this bad reputation we made the *COMPLETE* documentation and knowledge base available to anybody, at www.vbmigration.com.

Even better, we have uploaded tons of VB6 code samples paired with the corresponding VB.NET code that our VB Migration Partner generates, so that readers can see by themselves. Notice that these samples are real-world open source projects found on the Internet, rather than artificially built code examples that carefully highlights our tool&#039;s strengths and hide its weakness. 

As far as I know, no other vendor has take a similar candid approach, at least not to this extent, presumably because they can&#039;t offer such a high success ratio without in-depth edits to either the original VB6 code or the generated VB.NET code. Looking at the great response both during the beta test period and after the official launch, it is evident that the developer community appreciates this transparency.

Your last question - Are there better alternative like migrating to Delphi? - calls for a more detailed answer. I will reply on my own blog, at www.vbmigration.com/blog

thanks again,

   Francesco Balena
   The VB Migration Partner Team</description>
		<content:encoded><![CDATA[<p>Thank you for mentioning our tool, Dennis.</p>
<p>Let me add just one thought. Code conversion tools, especially VB6-to-VB.NET tools, suffer from a bad reputation of not being enough powerful or cost-effective. To counter this bad reputation we made the *COMPLETE* documentation and knowledge base available to anybody, at <a href="http://www.vbmigration.com" rel="nofollow">http://www.vbmigration.com</a>.</p>
<p>Even better, we have uploaded tons of VB6 code samples paired with the corresponding VB.NET code that our VB Migration Partner generates, so that readers can see by themselves. Notice that these samples are real-world open source projects found on the Internet, rather than artificially built code examples that carefully highlights our tool&#8217;s strengths and hide its weakness. </p>
<p>As far as I know, no other vendor has take a similar candid approach, at least not to this extent, presumably because they can&#8217;t offer such a high success ratio without in-depth edits to either the original VB6 code or the generated VB.NET code. Looking at the great response both during the beta test period and after the official launch, it is evident that the developer community appreciates this transparency.</p>
<p>Your last question &#8211; Are there better alternative like migrating to Delphi? &#8211; calls for a more detailed answer. I will reply on my own blog, at <a href="http://www.vbmigration.com/blog" rel="nofollow">http://www.vbmigration.com/blog</a></p>
<p>thanks again,</p>
<p>   Francesco Balena<br />
   The VB Migration Partner Team</p>
]]></content:encoded>
	</item>
</channel>
</rss>

