After much research it seems the wizard forces new sites to be created in this path. If anyone knows how to get around this please feel free to chime in. Specify alert settings. Here you can set up the SMTP server and reply-to address for alerts. The installer will proceed by itself This will install the plug-in to allow connections to the TFS server. Next, we need to make sure the service account has full control over the MachineKeys directory on the TFS server.
There should be just Administrators and Everyone in the Security tab. Make sure both have Full Control, then click Advanced. Click OK at the warning also. Log onto the MOSS box as an administrator, open up a command prompt and type the following commands:.
Open Visual Studio on the client machine. Expand the Source Control item on the left and click on the Plug-in Selection option. Holy installation, Batman! Now, to create a new Team Project try this:. Provide a name for the team project. Note this name will become part of the URL to the website, so to avoid HTML encoding use underscores and avoid symbols and spaces here.
Select the process template from the list. Project portal settings are next. The title will be the website title, so spaces and symbols are ok here. Note you cannot modify the project portal address. Specify your source control settings, either create a new empty repository, branch onto an existing repository, or skip source control altogether. The wizard will create your website, reporting, documentation, source control repository, and project.
This will open up Source Control Explorer. Select your machine and click Edit. Then click OK to map them. Here are some steps you can take first before hunting for your needle in a haystack:. Like I said, if anyone has an easier method of accomplishing this feel free to mention it. Otherwise this guide is the result of numerous trial and error steps that were documented as they happened. A final install from start to finish was conducted and it worked. I hope this helps whoever needs it!
For Instance Name I accepted the default. For the Startup Services I selected all five of them. For Collation Settings I accepted the default. I did not select any of the Error Report settings. After another reboot I was ready to install TFS After the splash screen and license agreement stuff, for Destination Folder I accepted the default.
For Database Server I accepted the default, which was the name of the local machine and was automatically filled in. For Alert Settings, I did not check anything. With my fingers crossed, I clicked Install, and after some time got a Success message. Next, after a reboot for safety, I installed Team Foundation Build. Here I followed the installation document exactly. After clicking Install, I eventually got a Success message.
By checking the System Event Log I noticed the error was something to the effect that a Server Scheduler could not contact the remote database. I tried various things without success. Well, there you have it. Once the TFS was up and running, I then created a Team Project, configured overall server group membership, added a Visual Studio Web Application Solution to the project typically forgetting to do a View Other Windows Pending Changes and checking in the new files, configured project membership, and manually created Workspace mappings on all the client machines in the training lab.
Accept all the defaults. The project takes about 5 minutes to create. Note: You can delete demo projects using the command-line utility tfsdeleteproject. After the project has been created, right-click on the project name and add a few accounts to the Project Administrators group, and add Domain Users to the Contributors group.
Now go to some client machine and create a file system based Web project. Build the project. You will have a Default. Connect to the TFS and select the appropriate project. Now, for each client machine, including the machine you used to create the Web project, you must create a Workspace. Note: a bogus Workspace will be created on the development machine.
Go to File Source Control Workspaces. In the source path, select the root of your project, not any sub-directories. In the destination path, select any convenient directory. Now you should be good to go. TFS will warn you that you are going to overwrite existing files in your destination directory, but that is usually what you want.
0コメント