Hi all

We are looking at implementing a TFS install fairly soon for our production source control. I've been looking at the eval version for the last week or so and have encountered a problem with one of the requirements I've been given.

We have an existing Sharepoint portal (2003) server that we have our company intranet on. We are trying to determine if it is possible to configure TFS to create project sites on the sharepoint server as opposed to the app tier.

If anyone has any feedback on this it would be much appreciated.

P.

With TFS V1, it is not possible to configure the project creation wizard to create the portal on a server different from the App tier.

However, we will be providing a whitepaper on the MSDN site in the near futrure, that will provide the steps to do this manually. I'm in the process of finding out the approximate time of release of this document and will let you know what I find.

Thanks!

Hi Yogita

Has the whitepaper been published yet? I have done a quick search but have not located it.

Thanks

Paul,

It looks like this whitepaper will be released either end of this week or early next week. Sorry about the delay!

Thanks!

As soon as this post was marked as answered nobody from TFS team seems to pay attention to it.

In my earlier post I had mentioned that it would be available that week. I just checked with the content team and looks like they are still working on the whitepaper. I apologize for the long wait and would appreciate your patience for another week.

Thanks!

Hello,
Thanks a lot for your patience. Here is the link to the whitepaper:

http://msdn.microsoft.com/vstudio/teamsystem/reference/technotes/tfs/conf_for_remote_ss.aspx

Hope this helps!

That's great - I look forward to getting this resolved.

Thanks for your help on this.

P.

FYI - this does work, but there were a couple of hiccups following the processes. Here's my feedback for anyone else that is trying to get this to work.

In step 7, the whitepaper tells you to modify the XML resulting from step 6. Don't bother with this - just modify the example XML that is provided.

On our server, a lot of these settings changes seemed to take some time to be reflected. Repeat step 6 after step 7 until the change you made is reflected in the settings retrieved from the server.

On our development projects, when a new project was created after the settings were changed, the Documents folder in Team Exploror was still pointing at the original server. I played around with this for a while, to no avail. I came back in the next morning and the setting was changed to the new server. It's caching somewhere, but couldn't figure out where. I created a new team project after this and it was fine.

I haven't run into any problems since this has been configured - I'm keeping my fingers crossed and will update this with any more information I come across.

Hi Paul,

We are trying to integrate with an external portal and encountered the same problems as you (posted here the day before yesterday but removed afterwards). However after having them fixed, we are still unable to create team projects. We verified that the changes are reflected in the settings retrieved from the server. Stopping iiserver and restarting VS before creating a new Team Project solved some of the caching problems.

What exactly do you mean with "just modify the example XML that is provided". Provided where ?

Thanks.

Peter.

Hi Peter

The XML I was referring to was contained in the whitepaper referenced earlier.

<RegistrationEntries>
<RegistrationEntry>
<Type>Wss</Type>
<ChangeType>Change</ChangeType>
<ServiceInterfaces>
<ServiceInterface>
<Name>WssAdminService</Name>
<Url>[protocol]://[AT server]:[port]/_vti_adm/admin.asmx</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseServerUrl</Name>
<Url>[protocol]://[AT server]</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseSiteUrl</Name>
<Url>[protocol]://[AT server]/sites</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseSiteUnc</Name>
<Url>\\[AT server]\sites</Url>
</ServiceInterface>
</ServiceInterfaces>
</RegistrationEntry>
</RegistrationEntries>

I'm not sure about any of the problems that you might be encountering with creating team projects - the only time I had a problem with that was when the registration entried had not yet been updated on the server. When the TFS server was attempting to create the project it failed on the creation of the Sharepoint portal due to the fact that Sharepoint services had been uninstalled and it didn't know to point to the sharepoint server - due to the registration entries being cached.

Once the caching was resolved, I was able to create a team project without any problems, although there was some strange behaviour around the listed location of the project portal.

Sorry if this doesn't help, but possibly if you haven't made it through this problem yet you could provide some more detail?

Paul

Could someone send me the white paper. Apparantly its under revision on the web site.

Regards

Darren

The white paper is still under revision. Could anyone send it to me?

Thanks a lot