<?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>Orcas Team Build:  WCF web services replace .NET remoting</title><link>http://blogs.msdn.com/b/buckh/archive/2007/03/16/orcas-team-build-wcf-web-services-replace-net-remoting.aspx</link><description>In Visual Studio Team Foundation Server 2005 (v1), the communication from the application tier (AT) to the build computer used .NET remoting. This was the only component in Team Foundation Server that used .NET remoting, as all other communication used</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>HTTP 502 error when the server tries to connect to the build agent to start a build</title><link>http://blogs.msdn.com/b/buckh/archive/2007/03/16/orcas-team-build-wcf-web-services-replace-net-remoting.aspx#7492922</link><pubDate>Wed, 06 Feb 2008 18:54:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7492922</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;The following came up a couple of weeks ago, and I thought it would be worth posting for anyone else&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=7492922" width="1" height="1"&gt;</description></item><item><title>TFS 2008: Build agent configuration options</title><link>http://blogs.msdn.com/b/buckh/archive/2007/03/16/orcas-team-build-wcf-web-services-replace-net-remoting.aspx#3983558</link><pubDate>Sat, 21 Jul 2007 05:11:18 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3983558</guid><dc:creator>Noticias externas</dc:creator><description>&lt;p&gt;While some of the build agent properties are available in the VS GUI, buried in the tfsbuildservice.exe&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3983558" width="1" height="1"&gt;</description></item><item><title>TFS 2008: Build agent configuration options</title><link>http://blogs.msdn.com/b/buckh/archive/2007/03/16/orcas-team-build-wcf-web-services-replace-net-remoting.aspx#3983415</link><pubDate>Sat, 21 Jul 2007 05:03:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:3983415</guid><dc:creator>Buck Hodges</dc:creator><description>&lt;p&gt;While some of the build agent properties are available in the VS GUI, buried in the tfsbuildservice.exe.config&lt;/p&gt;
&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=3983415" width="1" height="1"&gt;</description></item><item><title>VSTS Links - 03/19/2007</title><link>http://blogs.msdn.com/b/buckh/archive/2007/03/16/orcas-team-build-wcf-web-services-replace-net-remoting.aspx#1912895</link><pubDate>Mon, 19 Mar 2007 16:09:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1912895</guid><dc:creator>Team System News</dc:creator><description>&lt;p&gt;The Teams WIT Tools Blog on Handling display name changes in Team Foundation Server. Brian Harry on...&lt;/p&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1912895" width="1" height="1"&gt;</description></item><item><title>re: Orcas Team Build:  WCF web services replace .NET remoting</title><link>http://blogs.msdn.com/b/buckh/archive/2007/03/16/orcas-team-build-wcf-web-services-replace-net-remoting.aspx#1900669</link><pubDate>Sat, 17 Mar 2007 18:15:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:1900669</guid><dc:creator>Buck Hodges</dc:creator><description>&lt;p&gt;For those of you who try the telnet exercise above, the March Orcas CTP still uses .NET remoting. &amp;nbsp;You'll see WCF web services in the first beta release, whenever that happens.&lt;/p&gt;
&lt;p&gt;Buck&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=1900669" width="1" height="1"&gt;</description></item></channel></rss>