TFS do not use SharepointSitesUri correctly - by et381

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


0
0
Sign in
to vote
ID 296731 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/5/2007 1:27:00 AM
Access Restriction Public

Description

After using the TFSAdminUtil.exe to point TFS Beta 2 to an existing WSS 3.0 farm.  TFS do not use the path set correctly if the path is anything other than /sites.

For example

TFS works correctly if SharepointSitesUri is set to http://somewssserver/sites, but does not work correctly when set to http://somewssserver/development/sites

We want to use an existing Sharepoint farm within the organisation and the path made available for use is http://wssserver/development/sites.


We think this url problem is also causing project creation to fail when configured to anything other than /sites for SharepointSitesUri
Sign in to post a comment.
Posted by et381 on 9/6/2007 at 1:30 PM
It is a managed path per TFS server, we just want the starting path to be 2 levels deep. So if it is by design to support only a single level managed path. Should make it more obvious and stop people from specifying a a managed path which is not just off the root.
Posted by Microsoft Connect on 9/6/2007 at 6:30 AM
In TFS 2008 You have to use managed paths per TFS server. Create managed path "Development" and set URI. More Info: http://blogs.msdn.com/sudhir/archive/2007/06/25/sharing-your-corporate-sharepoint-server-with-multiple-tfs-servers.aspx
Posted by Microsoft on 9/5/2007 at 8:13 PM
Thanks for your feedback. We have routed this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.

Thank you,
Visual Studio Product Team.
Posted by Microsoft on 9/5/2007 at 5:20 PM
Thank you for your feedback. We are currently investigating. If this issue is urgent, please call support directly (see http://support.microsoft.com).

Thank you,
Visual Studio Product Team