I have a rather large MVC2 project in TFS, which is automatically created during verification (Continuous Integration)
Currently, a fully-built version is dumped to a network resource on our IIS server. \\Server\wwwrootLatest
TFS, of course, creates many subfolders, because it just builds, it doesn’t even know that it is a drop folder, it is wwwroot.
This means that in order to actually use the assembly, we need to manually create an IIS application that points to the corresponding directory - which defeats the entire exercise object.
When we do manual publishing on this server, we use the “File System” as a method and simply overwrite the files in the UNC \\Server\wwwroot shared folder
(When publishing in other environments, we use full-featured MSDeploy.)
What I would like to do is convince TFS to publish the “File System” after the build is complete and duplicate what we do in the publication manually, for example:
The directory folder \\Server\Build , which will lead to something like \\Server\Build\Project\Date.Rev\
After this is completed, we want to publish it to \\Server\wwwrootLatest . Then we can configure the application, which will always contain the latest version, but if necessary, will have a full history.
The only examples I could find were to use the MSBuild commands in the assembly definition (excellent), but they all use MSDeploy for full-text publishing. I'm not sure how to automate what I want to do
Any help was appreciated.