<?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>Open Source and Visual Studio</title><link>http://blogs.msdn.com/dotnetinterop/archive/2005/12/07/open-source-and-visual-studio.aspx</link><description>Microsoft's forthcoming Visual Studio Team System will include source code control, integrated defect tracking, testing, reports, and a bunch of other project management and project governance tools and capabilities. All built in and integrated. BUT!</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Open Source and Visual Studio</title><link>http://blogs.msdn.com/dotnetinterop/archive/2005/12/07/open-source-and-visual-studio.aspx#501078</link><pubDate>Wed, 07 Dec 2005 20:23:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:501078</guid><dc:creator>Arne Claassen</dc:creator><description>I've been using perforce at work for over a year now and find it to be the best source control system I've used. There SCM plug-in is fantastic and allows it to work great with VS.NET. Of course that's off-topic... &lt;br&gt;&lt;br&gt;For my home projects I was going to use SVN or CVS, but couldn't find a good VS.NET integration. Sure AnkSVN is a very nice tool, but it works as an Add-in instead of in conjunction with with the Source Control paradigm of Visual Studio.&lt;br&gt;&lt;br&gt;From my digging around the net, it seems that the lack of good Open Source Source Control integrations stems from the licensing terms of the SCM API. Is that something that could be addressed, or is that just going to be a philosopical rift that's going to continue? Or am i simply not finding the Open Source SCM implementations?</description></item><item><title>re: Open Source and Visual Studio</title><link>http://blogs.msdn.com/dotnetinterop/archive/2005/12/07/open-source-and-visual-studio.aspx#501455</link><pubDate>Thu, 08 Dec 2005 10:07:35 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:501455</guid><dc:creator>Martin Woodward</dc:creator><description>While it is a commercial product, I'm working on an interesting product called Teamprise (&lt;a rel="nofollow" target="_new" href="http://www.teamprise.com"&gt;http://www.teamprise.com&lt;/a&gt;) which is a java implementation of the Team System client allowing you to do Visual Studio Team System Team Foundation Server operations (such as Source Control) from within Eclipse or a stand-alone java client - even running on Linux and Mac OS X.  &lt;br&gt;&lt;br&gt;All this is made possible because the Team Foundation Server exposes its services via a Web Service API.  Ain't this interop thing great!</description></item><item><title>re: Open Source and Visual Studio</title><link>http://blogs.msdn.com/dotnetinterop/archive/2005/12/07/open-source-and-visual-studio.aspx#501775</link><pubDate>Fri, 09 Dec 2005 01:30:01 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:501775</guid><dc:creator>AsbjornM</dc:creator><description>Nothing beats Subversion!&lt;br&gt;TortoiseSVN is an great tool for svn usage:&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://tortoisesvn.sourceforge.net/"&gt;http://tortoisesvn.sourceforge.net/&lt;/a&gt;&lt;br&gt;(Not tested Ankh yet)&lt;br&gt;&lt;br&gt;Other tools in use here: Nunit+testdriven.net, reflector, ndoc etc..&lt;br&gt;Since the pricing MS has on the teamsuite/teamsystem is so high we got to use alternatives, and no problem since the alternatives are so good! :)</description></item><item><title>re: Open Source and Visual Studio</title><link>http://blogs.msdn.com/dotnetinterop/archive/2005/12/07/open-source-and-visual-studio.aspx#515516</link><pubDate>Sat, 21 Jan 2006 00:46:44 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:515516</guid><dc:creator>Dino</dc:creator><description>@Arne - no, I don't believe there is any special restriction wrt the SCM API.  Check out the VS SDK for details.&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://msdn.microsoft.com/vstudio/extend/default.aspx"&gt;http://msdn.microsoft.com/vstudio/extend/default.aspx&lt;/a&gt;</description></item><item><title>With .NET, all the choices are provided by Microsoft</title><link>http://blogs.msdn.com/dotnetinterop/archive/2005/12/07/open-source-and-visual-studio.aspx#529538</link><pubDate>Fri, 10 Feb 2006 18:09:03 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:529538</guid><dc:creator>All About Interop</dc:creator><description>With .NET, all the choices are provided by Microsoft &lt;br&gt;Excuse the headline. I got a comment in a previous...</description></item></channel></rss>