When I came accross this issue none of the provided answers solved this problem or if it did I didn’t like recreating the project. The way I ended up solving the issue: Clicking on the “Connect to Team Projects button” (The plug next to the home button in the Team Explorer tab) Right click the … Read more
Here’s the deal: We have to tell both NuGet and TFS to ignore the packages, because NuGet is trying to do source-control related stuff that it absolutely shouldn’t be doing (bad form, Microsoft!). So you have to do two things. First, add a file named .tfignore to the solution folder (note the lack of s … Read more
For anyone having the same issue a work around is to undo your pending changes. When you get the confirmation dialog choose “No to all”. Only your pending changes should be left.
Unfortunately sharing of the Publish Profile is not supported or implemented in MSBuild. The logic to publish from the profile is contained in VS itself. Fortunately the profile doesn’t contain much information so there are ways to achieve what you are looking for. Our targets do not specifically support the exact same steps as followed … Read more
First, please make sure your .tfignore file created without any problem. This file does not have any suffix. One way to create it suggest you to rename a new.txt file with “tfignore.” It will auto change to right .tfignore file. You can also use the auto automatically generated .tfignore file, follow below steps: In the … Read more
Update: Now you should use below to avoid syncing sources at all: Classic Editor: agent.source.skip=true YAML: steps: – checkout: none It’s not able to directly disable/remove the Get Sources task. However, you could add a variable to achieve it: Build.SyncSources = false You can see from below screenshot, the Get Sources operation started and finished … Read more
We practice highly componentised development using Java, we have about 250 modules in trunk that have independent life cycles. Dependencies are managed through Maven (that’s a best practice right there), every iteration (bi-weekly) actively developed modules get tagged with a new version. 3 digit version numbers with strict semantics (major.minor.build – major changes means backwards … Read more
msbuild test.sln /t:project /p:Configuration=”Release” /p:Platform=”x86″ /p:BuildProjectReferences=false Notice that what is assigned to /t is the project name in the solution, it can be different from the project file name. Also, as stated in How to: Build specific targets in solutions by using MSBuild.exe: If the project name contains any of the characters %, $, @, … Read more
Use the command line utility TF – Team Foundation Version Control Tool (tf). You can get a list of all workspaces by bringing up a Visual Studio Command Prompt then changing to your workspace folder and issuing the following commands: C:\YourWorkspaceFolder>tf workspaces /owner:* You should see your problem workspace in the list as well as … Read more
For those of us not living inside build templates every day here’s the steps that got it working for me: First find the template associated with your build (if you already know where to find it skip a couple steps). Just right click the build definition and select Edit build definition Select the Process tab … Read more