After playing around a bit - I was able to rename the sub-folders in my projects in Team Foundation Server but it will not let me rename the root project folder. Any ideas why? Below is a screen shot to illustrate the problem.
As you can see I was able to rename the folder under UniversalCheckInApp to UniversalCheckInKiosk but I cannot rename its parent folder as the rename option is disabled when I right click on that folder. Some more information - Dev folder that is the parent of UniversalCheckInApp is not mapped but the UniversalCheckInApp folder is mapped to a local folder. Any assistance would be greatly appreciated.
OK so after playing some more - I was able to figure it out. I had to do a mapping at the Dev folder level. Then the rename option became available for the UniversalCheckInApp folder. It would be really nice if Microsoft would work on a better way of doing this.
Related
Hey guys!
I am trying to upload my project to our TFS server and then my intention is of course to build it...
The thing is: When I go to Code->project_name and I click on "Upload files" it only adds the files in the current folder. I know it can't be the case that I have to create tens of folders and then add the relevant files to it as shown in the original folder.
How do I do that without uploading all of the files? the build fails if I only upload a .sln file.
I am totally new to is so I really don't know how to use it...
I tried to do it via the VS but It gives me some weird errors.
Any help would be appreciated.
*Using TFS 2018.
Thanks!
If you're using TFVC, map a workspace on your machine and add the code there, then check it in.
When I create a MVC project in Visual Studio, it will automatically generate a solution folder with the same name alone with .sln file, packages folder.
For example:
/MyProject/MyProject
and when I run the application in server:
http://XXXXX/MyProject/MyProject
I hate the address. I want to the address looks like:
http://XXXXX/MyProject
I tried to move the solution folder to upper level directory, however, the MVC project can still run but show errors and many warnings.
Is there any way I can create a MVC and I can specify the solution folder? or I can relocate the MVC solution folder nicely?
Thanks
You can relocate sln file.
Just close solution, move sln file to project folder, and then open sln file in VS.
Project will not load. Delete unloaded project in Solution Explorer, then right click on solution (in Solution Explorer) Add => existing project...
and select .csproj file of the project.
Rebuild application, nuget will restore packeges.
But I don't know why You hate path.
You can name solution folder with diffrent name then Your project. when You add more projects every project folder will be in one solution folder and path will looks like:
http://XXXXX/Solution/Project1
http://XXXXX/Solution/Project2
And one last thing: You probobly don't want whole solution in application server, you can just deploy project as web deploy packege.
One of our developers is unable to see a file in TFS Source Control Explorer, yet myself and another developer can on our machines. The file is clearly there but for some reason it is not being displayed to this one developer, all other files in the folder are displayed correctly. He's set up as a project admin so it doesn't look like a permissions thing.
We're using VS 2013 Ultimate with TFS 2013 (Express). Anyone have any ideas?
Many thanks.
Have u looked at the project proj file to see if it's there? If not ,
unload the project and edit and add the reference of the file in the proj file.
This situation is often related to the Permission . Please use tf permission command to list the related permission of that folder with the user.
It may also be that the user has an odd workspace mapping.
For example given a source path $/project/folder1/folder2
A mapping like this
$/project/folder1/* c:\workspace
would show you all the files under folder1 and the directory name folder2 but files under folder2 would not show up in the workspace.
I have reorganised a solution that was created by someone else. The .sln file was in the directory of a website project (the old one without a .csproj file). I unbound the entire solution from TFS and then saved the .sln to a directory one level above.
What is the best way of getting this back into TFS so that other developers can pick up the changes in the .sln and folder locations?
Right click .sln file in Source Control Explorer and select Move, move the .sln to a directory one level above and check in the changes.
The default configuration of the Team Build Number Format is:
$(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
It drops all output to \\foo\bar\MyBuildDef_20111031.1 Great stuff so far!
The small problem is that it drops all binaries in that directory without a good indication of the dependencies of the binaries.
How can you modify this property, or otherwise, to have the solution's binaries dropped in their respective project directories?
In the case above, I had expected the MVC website (complete with its bin directory) to be dropped. Instead, we got that PLUS the extra drop of the binaries in the root.
In other words: TFS, please stop dropping all binaries in the root; it looks messy, and it's confusing on which files belong/associated with what.
How can this be achieved with Team Build 2010?
This blog post should help you out: http://blogs.msdn.com/b/willbar/archive/2011/02/05/splitting-team-build-outputs-into-folders.aspx
Essentially, you create a new 'Platform' for each project. Team Build will put each platform in a different directory by default, so you get a different directory for each of your projects.
Build configuration dialog:
Drop folder output:
Unfortunately I have not found a good way to do this yet, though it has been a while since I tried to find a better solution then what I settled on.
Current have solutions for each desktop application, and one with all the websites. I then followed the instructions here to make each solution output into a separate folder.