<?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>Ameyab's Blog : Visual Studio Team System 2005</title><link>http://blogs.msdn.com/ameyab/archive/tags/Visual+Studio+Team+System+2005/default.aspx</link><description>Tags: Visual Studio Team System 2005</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Understanding the TFS cube</title><link>http://blogs.msdn.com/ameyab/archive/2007/05/01/understanding-the-tfs-cube.aspx</link><pubDate>Wed, 02 May 2007 02:00:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:2364756</guid><dc:creator>Ameya</dc:creator><slash:comments>1</slash:comments><comments>http://blogs.msdn.com/ameyab/comments/2364756.aspx</comments><wfw:commentRss>http://blogs.msdn.com/ameyab/commentrss.aspx?PostID=2364756</wfw:commentRss><description>&lt;P&gt;Jimmy's first blog post (&lt;A href="http://blogs.msdn.com/teams_wit_tools/archive/2007/04/30/understanding-the-tfs-cube.aspx" mce_href="http://blogs.msdn.com/teams_wit_tools/archive/2007/04/30/understanding-the-tfs-cube.aspx"&gt;http://blogs.msdn.com/teams_wit_tools/archive/2007/04/30/understanding-the-tfs-cube.aspx&lt;/A&gt;)&amp;nbsp;on the Team blog explains the structure of the TFS cube! He covers four perspectives*&amp;nbsp;in great detail. &lt;/P&gt;
&lt;P&gt;*"Perspectives" is a great feature in SQL Server 2005 (Enterprise Edition) that groups the subset of related cube entities, such as measure groups and dimensions, into views; it makes it&amp;nbsp;easier to navigate the cube. You can learn more about perspectives here: &lt;A href="http://msdn2.microsoft.com/en-us/library/ms175338.aspx" mce_href="http://msdn2.microsoft.com/en-us/library/ms175338.aspx"&gt;http://msdn2.microsoft.com/en-us/library/ms175338.aspx&lt;/A&gt;.&lt;/P&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=2364756" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/ameyab/archive/tags/Reporting/default.aspx">Reporting</category><category domain="http://blogs.msdn.com/ameyab/archive/tags/Visual+Studio+Team+System+2005/default.aspx">Visual Studio Team System 2005</category><category domain="http://blogs.msdn.com/ameyab/archive/tags/Cube/default.aspx">Cube</category></item><item><title>Project Server 2003 and Visual Studio Team System 2005 connector available!</title><link>http://blogs.msdn.com/ameyab/archive/2006/10/18/project-server-2003-and-visual-studio-team-system-2005-connector-available.aspx</link><pubDate>Wed, 18 Oct 2006 23:56:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:840150</guid><dc:creator>Ameya</dc:creator><slash:comments>6</slash:comments><comments>http://blogs.msdn.com/ameyab/comments/840150.aspx</comments><wfw:commentRss>http://blogs.msdn.com/ameyab/commentrss.aspx?PostID=840150</wfw:commentRss><description>&lt;P&gt;A year ago I posted a sample application on &lt;A class="" href="http://www.gotdotnet.com/Workspaces/Workspace.aspx?id=b9f69ea5-ace1-4a21-846f-6222a507cc9c" target=_blank mce_href="http://www.gotdotnet.com/Workspaces/Workspace.aspx?id=b9f69ea5-ace1-4a21-846f-6222a507cc9c"&gt;GotDotNet&lt;/A&gt; to illustrate how Project Server and Visual Studio Team System can share data. The solution source code was accompanied by a detailed white paper that documented the architecture, design and the implementation. &lt;/P&gt;
&lt;P&gt;The goal for the solution was two fold. One, to illustrate how these two products could be "connected" to enable application development lifecycle management from conception to conclusion and two, to provide developers who were planning on developing a connector for the two systems with a "springboard". &lt;/P&gt;
&lt;P&gt;The posted solution works with the Beta 2 version of VSTS and the upgrade was left as a user exercise. Unfortunately, I did not have the cycles to update the solution myself. So the GotDotNet solution, while interesting, was not very useful for those who wanted to use it&amp;nbsp;without redeveloping parts of it - especially after VSTS was released. &lt;/P&gt;
&lt;P&gt;I am pleased to announce that Avanade has released an upgraded version of the connector. The upgraded connector is available at &lt;A class="" href="http://www.gotdotnet.com/workspaces/workspace.aspx?id=b9f69ea5-ace1-4a21-846f-6222a507cc9c" target=_blank mce_href="http://www.gotdotnet.com/workspaces/workspace.aspx?id=b9f69ea5-ace1-4a21-846f-6222a507cc9c"&gt;here&lt;/A&gt;. &lt;SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"&gt;The connector is also available as a part of the Avanade Software Lifecycle Platform™. You can learn more about it &lt;A href="http://msdn.microsoft.com/vstudio/why/avanade/default.aspx"&gt;here&lt;/A&gt;.&lt;/SPAN&gt;&lt;/P&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;SPAN style="FONT-WEIGHT: normal; FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'; mso-bidi-font-weight: bold"&gt;The &lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: 'Arial','sans-serif'"&gt;connector synchronizes&amp;nbsp;Project, Resource and Task data between the two systems. Project Managers, Resource Managers continue to work in the EPM environment while the development team works in the development environment, i.e. VSTS, and data seamlessly flows between the two systems. Updates to work items in VSTS are automatically applied to the corresponding assignments and tasks in Project Server and vice versa. Project Managers have complete control over the inflow of the actuals into the project plan. &lt;SPAN style="mso-spacerun: yes"&gt;&amp;nbsp;&lt;/SPAN&gt;In addition, resource management functions for all development projects, like managing time and utilization for resources working across multiple projects, team staffing etc. can be performed in Project Server. Lastly, portfolio and program level reports can easily be generated for projects being executed in VSTS and managed in Project Server. &lt;?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;SPAN style="FONT-SIZE: 10pt; COLOR: #333333; FONT-FAMILY: 'Arial','sans-serif'; LETTER-SPACING: 0.25pt"&gt;&lt;o:p&gt;&lt;/o:p&gt;&lt;/SPAN&gt;&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=840150" width="1" height="1"&gt;</description><category domain="http://blogs.msdn.com/ameyab/archive/tags/Project+Server+2003/default.aspx">Project Server 2003</category><category domain="http://blogs.msdn.com/ameyab/archive/tags/Connector/default.aspx">Connector</category><category domain="http://blogs.msdn.com/ameyab/archive/tags/Visual+Studio+Team+System+2005/default.aspx">Visual Studio Team System 2005</category></item></channel></rss>