<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Recruiting VB.NET developers</title>
	<atom:link href="http://3poundmass.wordpress.com/2007/08/20/recruiting-vbnet-developers/feed/" rel="self" type="application/rss+xml" />
	<link>http://3poundmass.wordpress.com/2007/08/20/recruiting-vbnet-developers/</link>
	<description>Web development with Microsoft technologies</description>
	<lastBuildDate>Mon, 16 Nov 2009 05:06:59 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jfrankcarr</title>
		<link>http://3poundmass.wordpress.com/2007/08/20/recruiting-vbnet-developers/#comment-50</link>
		<dc:creator>jfrankcarr</dc:creator>
		<pubDate>Mon, 27 Aug 2007 14:27:58 +0000</pubDate>
		<guid isPermaLink="false">http://3poundmass.wordpress.com/2007/08/20/recruiting-vbnet-developers/#comment-50</guid>
		<description>I agree with your final point that the key is understanding the .NET Framework and having good development practices. However, I don&#039;t think that hiring a C# developer to do VB.NET programming is a particularly good idea. 

First, you would have a hard time convincing them to take the job and stick with it unless they were desperate for work or if you promised them that you were converting from VB.NET to C#. 

Secondly, there are a number of very worthwhile and useful parts of the Microsoft.VisualBasic namespace along with the not-so-great legacy features. Even some legacy functions, like Mid, can be useful in some situations. The trick for the good VB.NET developer is to know what to use, what not to use and when to use it. A C# programmer is likely to simply throw out anything that carries a &quot;VB stigma&quot;, including parts of the core language, which can easily result in VB code as inefficient as overuse of VB6 methods.</description>
		<content:encoded><![CDATA[<p>I agree with your final point that the key is understanding the .NET Framework and having good development practices. However, I don&#8217;t think that hiring a C# developer to do VB.NET programming is a particularly good idea. </p>
<p>First, you would have a hard time convincing them to take the job and stick with it unless they were desperate for work or if you promised them that you were converting from VB.NET to C#. </p>
<p>Secondly, there are a number of very worthwhile and useful parts of the Microsoft.VisualBasic namespace along with the not-so-great legacy features. Even some legacy functions, like Mid, can be useful in some situations. The trick for the good VB.NET developer is to know what to use, what not to use and when to use it. A C# programmer is likely to simply throw out anything that carries a &#8220;VB stigma&#8221;, including parts of the core language, which can easily result in VB code as inefficient as overuse of VB6 methods.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
