<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" media="screen" href="/styles/xslt/rss.xslt"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:c9="http://channel9.msdn.com">
<channel>
	<title>Channel 9 Forums - Coffeehouse - VB.Net + C# code in one project?</title>
	<atom:link rel="self" type="application/rss+xml" href="http://channel9.msdn.com/Forums/rss"></atom:link>
	<image>
		<url>http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.png</url>
		<title>Channel 9 Forums - Coffeehouse - VB.Net + C# code in one project?</title>
		<link>http://channel9.msdn.com/Forums</link>
	</image>
	<description>Channel 9 keeps you up to date with the latest news and behind the scenes info from Microsoft that developers love to keep up with. From LINQ to SilverLight – Watch videos and hear about all the cool technologies coming and the people behind them.</description>
	<link>http://channel9.msdn.com/Forums</link>
	<language>en</language>
	<pubDate>Sat, 18 May 2013 17:58:05 GMT</pubDate>
	<lastBuildDate>Sat, 18 May 2013 17:58:05 GMT</lastBuildDate>
	<generator>Rev9</generator>
	<c9:totalResults>3</c9:totalResults>
	<c9:pageCount>-3</c9:pageCount>
	<c9:pageSize>-1</c9:pageSize>
	<item>
		<title>Coffeehouse - VB.Net + C# code in one project?</title>
		<description><![CDATA[<p>I read on another board that adding the ability to move VB.Net and C# modules into one project is being considered. I am curious about what everyone else thinks about this suggestion? Would it make .Net code more portable or simple act to confuse projects?</p>]]></description>
		<link>http://channel9.msdn.com/Forums/Coffeehouse/1506-VBNet--C-code-in-one-project/1506#1506</link>
		<pubDate>Fri, 09 Apr 2004 21:36:32 GMT</pubDate>
		<guid isPermaLink="false">http://channel9.msdn.com/Forums/Coffeehouse/1506-VBNet--C-code-in-one-project/1506#1506</guid>
		<dc:creator>Manip</dc:creator>
		<slash:comments>3</slash:comments>
		<wfw:commentRss>http://channel9.msdn.com/Niners/Manip/Discussions/RSS</wfw:commentRss>
	</item>
	<item>
		<title>Coffeehouse - VB.Net + C# code in one project?</title>
		<description><![CDATA[<p>I'm not sure how much of a difference it would really make. As it is you can create a class in one language and use it in a program written in a different language. You can even create&nbsp;a new class in C# that inherits a class written in VB and use the new
 class in a J# program. You can put all the classes in one solution (individual projects in different languages) so they all compile together as well.</p>]]></description>
		<link>http://channel9.msdn.com/Forums/Coffeehouse/1506-VBNet--C-code-in-one-project/9f514107239242c69a8e9dea0112db73#9f514107239242c69a8e9dea0112db73</link>
		<pubDate>Sat, 10 Apr 2004 00:57:52 GMT</pubDate>
		<guid isPermaLink="false">http://channel9.msdn.com/Forums/Coffeehouse/1506-VBNet--C-code-in-one-project/9f514107239242c69a8e9dea0112db73#9f514107239242c69a8e9dea0112db73</guid>
		<dc:creator>AlfredTh</dc:creator>
		<slash:comments>3</slash:comments>
		<wfw:commentRss>http://channel9.msdn.com/Niners/AlfredTh/Discussions/RSS</wfw:commentRss>
	</item>
	<item>
		<title>Coffeehouse - VB.Net + C# code in one project?</title>
		<description><![CDATA[<p>I was going to say basically what Alfred said, but didn't want to assume too much as it's been a few months since I did any .NET development.<br>
<br>
The strength of .NET, and the reason I switched to it was the multi-lingual capabilities.<br>
<br>
In fact, when our team (at my last job) first switched we had one J# guy, a C# guy (previously C&#43;&#43;), a VB.NET guy and a guy who used Borland's Delphi extension.<br>
<br>
It worked great. Over time everyone switched to C# for standardization and ease of documentation (I also 'pushed' them a little because I dind't want to have to maintain a J# position). But, everything always worked great together.<br>
<br>
It's definitely one of my favourite things about .NET, because it eliminates most people's biggest fear: learning a new language. They just need to learn the Framework (and the IDE, but VS.NET makes both of these incredibly easy).</p>]]></description>
		<link>http://channel9.msdn.com/Forums/Coffeehouse/1506-VBNet--C-code-in-one-project/014513c8548947f492729dea0112dba2#014513c8548947f492729dea0112dba2</link>
		<pubDate>Sat, 10 Apr 2004 01:11:24 GMT</pubDate>
		<guid isPermaLink="false">http://channel9.msdn.com/Forums/Coffeehouse/1506-VBNet--C-code-in-one-project/014513c8548947f492729dea0112dba2#014513c8548947f492729dea0112dba2</guid>
		<dc:creator>Jeremy W</dc:creator>
		<slash:comments>3</slash:comments>
		<wfw:commentRss>http://channel9.msdn.com/Niners/Jeremy W/Discussions/RSS</wfw:commentRss>
	</item>
</channel>
</rss>