When ever I open a project, all my local files are replaced with TFS server files. And all the local files will have current datestamp.
For testing I unmaped the project , then all the local files automatically deleted.
I am working of many projects, but this issue is with only this project
Note : Tools > Options > Source Control > Enviornment > 'Get everything when a soulution or project is opend' has default value. ie. unchecked.
TFS Version : 2018,
Visual Studio Version : 2013
Related
I have upgraded my company's TFS from 2013 to 2017. We still have our old XAML build definitions but are moving to the new JSON templates.
Most of the build definitions are working fine but some don't act like the former XAML definitions. I get all of the compiled assemblies in the $(Build.BinariesDirectory) folder but if I have a csproj that has Content items set to CopyAlways, they get copied to $(Build.SourcesDirectory), but they do not get copied into the $(Build.BinariesDirectory) for MSBuild. Project set up in Visual Studio
When building the old XAML build definitions they are copied to the bin directory fine: Build agent with the copied content
I have tried changing versions from 15 to the older 14 which still did not resolve this situation.
If you mean using the vNext build system, then you can add below msbuild arguments in the MSBuild Arguments area of the Visual Studio Build or MsBuild task to get the target files copied to the binaries directory.:
/p:OutputPath=$(Build.BinariesDirectory)
Note: The output is going to the \b\ folder, as the value of the variable $(Build.BinariesDirectory) is something like c:\agent\_work\1\b.
Build.BinariesDirectory :
The local path on the agent you can use as an output folder for
compiled binaries. For example: c:\agent\_work\1\b.
Source: Predefined variables
After updated my TFS 2013 server to Update 4 i can't create anymore any team project inside visual studio. I receiving this error. I searched in entire network and already deleted my cache folder and changes xml agile file to false Like says in this page.
Resolved.
I downloaded C:\Program Files\Microsoft Team Foundation Server 12.0\Tools\Deploy\ProcessTemplateManagerFiles\1033\MsfAgile\Template.zip and unziped. In Xml file put all to false.
In my computer and in TFS Explorer > Settings > Process Manager Template Upload folder again and all works.
This is a winform application.
All dlls, exe and some other extension files are copied to the StartupProject\bin through the post build events(VS post-build).
On TFS Server, the project has 2 subfolders: bin and src.(bin contains required dlls, but other extensions are missing -.png, .dat, .xslx).
On the server, the post build copied files appear under the StartupProject\bin, but they are not copied to TFSFolder\bin.
How can I force copy all the StartupProj/bin to the TFSFolder\bin?
Team Build use a different directory layouts from Visual Studio builds. All Binaries go in a single folder for any project built, so references are automatically solved and it is easy to copy the DLL to the final Drop folder.
You should use $(OutDir) MSBuild variable to properly reference the binaries directory in VS and TFS builds. See Is there a single MSBuild and TFSBuild variable that will point to where the binaries are? for some details.
If you need to use different scripts for desktop (VS) and server (TFS) builds, use the $(BuildingInsideVisualStudio) variable as explained in TFS 2010 Build Automation and post-build event.
I am trying to modify my project so that on build it queries for the current TFS changeset for the local directory and uses that to form the build number (using http://florent.clairambault.fr/insert-svn-version-and-build-number-in-your-c-assemblyinfo-file as a reference).
Since we currently are not using team build or any continuous integration for this particular project at this time I plan to use:
tf history . /r /noprompt /stopafter:1 /version:W
However, when I test this command out using the visual studio command prompt in my project's directly (where I work from TFS) it claims:
There is no working folder mapping for xxxxxxxx
The folder is shown as mapped in my workspaces in Visual Studio's Source Control Explorer (shows as the local path), and when I edit my workspace.
Why is the command line utility claiming there is no working folder when it is?
You will see this error message if you are using Visual Studio 2012 (and the corresponding Team Explorer 2012 client) and you are using tf.exe from Team Explorer 2010.
TFS 2010 clients store their local workspace cache in a different location on-disk than TFS 2012 clients. Thus, if you are to create a workspace with a TFS 2012 client, the TFS 2010 client cannot see that workspace data until it has connected to the server and populated its own local client cache.
It sounds like you're okay with using the TFS 2012 version of tf.exe, so I would make sure that your PATH contains an entry to that one first, and this should resolve your problem.
If you really wanted interoperability between the two versions, you would need to make sure to connect to your TFS server from both clients in order to make sure the workspace cache was complete for both. However make sure that you are using only server workspaces in this case, as TFS 2010 cannot connect to a TFS 2012 local workspace.
I've set up "Team Foundation Build" (I think that's the correct name). I have a build controller (build machine) that has been building our solution correctly. When building on the build machine, I'm using a separate solution configuration.
We added a new project to the solution. I've opened the configuration manager and checked the box for "Build" next to that new project while the configuration used on the build machine is selected. This change to the solution is checked in. But the build machine won't build that project.
If I make changes to solution configurations and examine the .sln file, I see those changes reflected so I know that information is stored there. However, when I open the .sln file in Visual Studio on the build machine (after it's written there during a failed build), I see that the check box "Build" next to our new project is unchecked (thus explaining why it's not being built). If I copy the .sln file from the build machine to my machine and compare it with the .sln on my machine (where the box is checked), they match!
I'm baffled...
It's likely that the new project is in a folder in source control that is not specified in the TFS Build's definition's list of workspaces.
Edit the TFS Build definition and verify the list of working folders.
The solution file may contain this project reference but unless it is included in the working folders it will not be available to the build server.