can anyone just asnwer my question
I have asked in two different posts versions of the same question and so far no answer....
can I put an asp.net web site and team server on the same server.
for example:
team.domain.com 192.168.1.10 port 80
newweb.domain.com 192.168.1.10 port 80
and then from a client pc with VS and Team client installed edit the web project and have a team project that publishes builds to that "newweb"
for example I normally have to put frontpage server ext. on a remote server to edit files and update the web site.
can team system hold the code files and publish them to the iis web site
how do I do that!
that's what I need to know and so far I have not seen ZIP on how to do it.
Thanks!

Developing on Same Server as Team Foundation Server
Manickam
What I want to acheive is developers working on their own workstations and checking in to TFS. a nightly build will be scheduled and the drop directory will be a location on the build server set to run as an ASP.Net application.
I have run a couple of builds and noticed that it dynamically creates directories with a date & build number appended. I presume that I would need to add some Copy statements to the build xml file.
sg60
http://tfs:8080/Build/v1.0/BuildStore.asmx
Invoke the "GetListOfBuilds" web method from this web service. It provides info about each build, including the location of the share for build drops. When invoking this web method, enter the Team Project name and Build Type (e.g., "Nightly").
Is this what you require
- Vasu
Victor DelPrete
Brian
Rajasekhar
My issue is not really with the build process since that works. My issue would be with the drop location since Team Build appends infomration to this which would mean either scripting IIS or copying the build output to another directory.
The original poster on this thread has a different issue, in that he wants to use Hostnames to allow multiple websites on the same server as TFS. I believe this should be possible, however VS.Net should be configured to use a fileshare to access the development site as opposed to using FP extensions.