{"id":2763,"date":"2007-02-28T08:00:00","date_gmt":"2007-02-28T08:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/buckh\/2007\/02\/28\/schema-for-the-workspacemapping-xml-file\/"},"modified":"2007-02-28T08:00:00","modified_gmt":"2007-02-28T08:00:00","slug":"schema-for-the-workspacemapping-xml-file","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/buckh\/schema-for-the-workspacemapping-xml-file\/","title":{"rendered":"Schema for the WorkspaceMapping.xml file"},"content":{"rendered":"<p>The WorkspaceMapping.xml file is one of the files generated when creating a new build type.&nbsp; Those of you who&#8217;ve had to customize a build are probably familiar with the <a href=\"http:\/\/msdn2.microsoft.com\/en-us\/library\/ms400710(VS.80).aspx\">TfsBuild.proj<\/a> file, which is the top-level file used to orchestrate the build.<\/p>\n<p>The WorkspaceMapping.xml file is used by one of the custom tasks to create the TFS workspace that contains the files to be built.&nbsp; In version 1 of Team Build, you must edit the WorkspaceMapping.xml file in order to change the mappings used by the workspace created for the build (in <a href=\"http:\/\/blogs.msdn.com\/buckh\/archive\/2007\/01\/06\/orcas-team-build-continuous-integration-spec-is-now-available.aspx\">Orcas<\/a>, you can do this in the GUI, and this file is no longer generated or used).<\/p>\n<p>There&rsquo;s no formal schema on MSDN.&nbsp; Here are the rules.<\/p>\n<ul>\n<li>The ServerItem should be a valid server path.<\/li>\n<li>The server paths must all be in the same team project.<\/li>\n<li>A server path can either be mapped or cloaked (for more information on mappings, see this <a href=\"http:\/\/msdn2.microsoft.com\/en-us\/library\/ms181378(VS.80).aspx\">MSDN topic on working folder mappings<\/a>).<\/li>\n<li>The local path for a mapped server item needs to be a legal local path, but it&rsquo;s otherwise completely ignored.&nbsp; This is an important difference between this workspace mapping template file and real source control mappings that you may be used to.<\/li>\n<li>Do not specify local paths for cloaked mappings.<\/li>\n<li>All cloaked paths must be children of mapped paths (cloaking is just a means of avoiding getting parts of an otherwise&nbsp;mapped tree).<\/li>\n<\/ul>\n<p>Here&#8217;s an example of a mapped and cloaked path.<\/p>\n<blockquote>\n<p><font face=\"Courier New\">&lt;?xml version=&#8221;1.0&#8243; encoding=&#8221;utf-8&#8243;?&gt;<\/font> \n<\/p>\n<p><font face=\"Courier New\">&lt;SerializedWorkspace xmlns:xsi=&#8221;http:\/\/www.w3.org\/2001\/XMLSchema-instance&#8221; xmlns:xsd=&#8221;http:\/\/www.w3.org\/2001\/XMLSchema&#8221;&gt;<\/font> \n<\/p>\n<p><font face=\"Courier New\">&nbsp; &lt;Mappings&gt;<\/font> \n<\/p>\n<p><font face=\"Courier New\">&nbsp;&nbsp;&nbsp; &lt;InternalMapping ServerItem=&#8221;$\/TeamProject\/Some\/Path&#8221; LocalItem=&#8221;c:thispathisignored&#8221; Type=&#8221;Map&#8221; \/&gt;<\/font> \n<\/p>\n<p><font face=\"Courier New\">&nbsp;&nbsp;&nbsp; &lt;InternalMapping ServerItem=&#8221;$\/TeamProject\/Some\/Path\/Cloaked&#8221; Type=&#8221;Cloak&#8221; \/&gt;<\/font> \n<\/p>\n<p><font face=\"Courier New\">&nbsp; &lt;\/Mappings&gt;<\/font> \n<\/p>\n<p><font face=\"Courier New\">&lt;\/SerializedWorkspace&gt;<\/font><\/p>\n<\/blockquote>\n<p>This post only applies to Team Foundation Server 2005. \n<\/p>\n<p>tags: <a href=\"http:\/\/technorati.com\/tag\/tfs\" rel=\"tag\">tfs<\/a>, <a href=\"http:\/\/technorati.com\/tag\/team+foundation\" rel=\"tag\">team foundation<\/a>, <a href=\"http:\/\/technorati.com\/tag\/team+build\" rel=\"tag\">team build<\/a><\/p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>The WorkspaceMapping.xml file is one of the files generated when creating a new build type.&nbsp; Those of you who&#8217;ve had to customize a build are probably familiar with the TfsBuild.proj file, which is the top-level file used to orchestrate the build. The WorkspaceMapping.xml file is used by one of the custom tasks to create the [&hellip;]<\/p>\n","protected":false},"author":94,"featured_media":10268,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[7,8],"class_list":["post-2763","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-team-build","tag-team-foundation"],"acf":[],"blog_post_summary":"<p>The WorkspaceMapping.xml file is one of the files generated when creating a new build type.&nbsp; Those of you who&#8217;ve had to customize a build are probably familiar with the TfsBuild.proj file, which is the top-level file used to orchestrate the build. The WorkspaceMapping.xml file is used by one of the custom tasks to create the [&hellip;]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts\/2763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/users\/94"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/comments?post=2763"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts\/2763\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/media\/10268"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/media?parent=2763"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/categories?post=2763"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/tags?post=2763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}