This question already has an answer here:
Closed 10 years ago.
Possible Duplicate:
Other users checkouts are not visible in Source Control Explorer (TFS Express)
For TFS 2010 I used Team Foundation SideKicks to check if someone in our team had files checked out.
In TFS2012 Team Foundation Sidekicks does not work anymore.
So i'm trying to figure out how to see if someone (anyone) has checked out files.
So I checked some files out myself, to test things.
First: In VS2012 > Source Control Explorer > Rightmouse on $\ (top root node) > Find > Find By Status > Path": $/, Wildcard left empy > Checked Recursive > Checked Status > Checked Display all checked out. > Find button.
Result: nonthing!!! No items found. HUH???????? How is this possible. I have checked out files, if i browse to that node, i see checked out files. What is going on here????????
Is this a bug???
Second: Command line:
tf.exe status $/ /s:http://[server]:8080/tfs /recursive
Message:
Changes from local workspaces will not be displayed when using the /user option
if a workspace is not supplied or if that workspace is on another machine.
There are no pending changes.
I think this is because we are using Local workspaces?
I want to still use local workspaces.
But how do i check if someone has files checked out?
Ok, I found the problem....
When you edit your workspace in vs2012, in the advanced view (click advanced button when editing your workspace), there is a property called 'Location'. This was set to 'Local'. When we set it to 'Server', all queries described above did work again.
Seems that this is a new feature in TFS2012/VS2012. And in the TFS2010/VS2010 age, the default was simular to 'Server'.
Problem solved....
Related
I have my source code in TFS.
The issue is that when i try to get the latest files from the TFS, I am made to wait for 5 minutes for connecting to server to get. and then it says timed out! Then i will have to connect to the TFS again.
Still not able to get the code!
I had tried mapping it to a different folder but even that failed.
I am using Visual Studio 2012 Express for web.
I have already tried clearing all the local data, cache and all that kind o stuff. I even tried resetting the user data.
Also tried logging in with another account to check weather if it was an issue with my Hotmail account(it's not. because i am not able to get it even with another Id).
Nothing helped!
Issue Fixed!
Here are the steps i did to fix it.
Since clearing all files may reset all your settings on visual studio, this should be the last possible option to do.
Just did a repair on the VS 2012,
cleared everything from
C:\Users\(Username)\AppData\Local\Microsoft\Team Foundation\4.0\Cache
Clear everything from
C:\Users\(Username)\AppData\Local\Microsoft\VisualStudio
Clear everything from
C:\Users\(Username)\AppData\Local\Microsoft\VSCommon
But here is another issue.
I had added a file by mistake to a different repo. I have deleted that from the server(Online). but the deleted project file is still shown in my source explorer in VS with a plus sign! How do i remove those?
if anyone have any idea, please help! Thanks a lot..!
Seems your project file still have some source control bindings. So that file can be detect as new add file in source control explorer. You need to remove source control bindings.
There is a tool to remove Source Control Bindings from Visual Studio Solutions and Projects from msdn: Remove Source Control Bindings from Visual Studio Solutions and Projects Detail steps as below:
Delete the .suo next to the .sln file, and then opened the .sln file in Notepad and deleted this entire section:
GlobalSection(TeamFoundationVersionControl) = preSolution
SccNumberOfProjects = 2
SccEnterpriseProvider = {xxxxx}
SccTeamFoundationServer = http://some-other-guys-tfs-server/
SccLocalPath0 = .
SccProjectUniqueName1 = xxDemo\\xxDemo.csproj
SccProjectName1 = xxDemo
SccLocalPath1 = xxDemo
EndGlobalSection
Save the .sln in Notepad and then open in Visual Studio.
More ways and more information for you reference: How can I completely remove TFS Bindings
Solution for the second question!
It was a misunderstanding of the pending Change.
I had deleted the folder from the server but the file names still appeared on the TFS source explorer on VS.
It was just because VS did recognize it as a pending change to be checked in even-though it wasn't one!
So just an undo pending changesdid the trick for me!
In TFS server have you set all privileges (access) for your account. If not then add Administrative access for your account on TFS.
My issue is that I cannot select a build process template after migrating to TFS/VS2012.
I managed to google and find one article which suggest the same problem here,
Possible Bug
Any ideas how I can get the dropdown to load the Build Process Templates or why they may not be getting loaded?
Also, I am able to click New->Copy Template, and copy successfully, but it never populates the dropdown list after accepting.
Possibly the same issue
I recently ran into the same problem but not related to upgrading the server. We were not able to see build process templates when trying to add a new build definition. We are in TFS 2012. This team project also appeared not to have any build definitions. That was expected though because we had not yet used the TFS builds on this team project.
The problem was caused by someone with admin rights setting the "View build definition" and the "View Builds" access rights to Deny for everyone.
By just setting that back to allow on the TFS group, we suddenly could see the build definitions and also were able to select build process templates.
It was really strange that it let us add new build process templates, but we couldn't select them.
Sooo...
I was finally able to get the templates loading by doing the following.
Unmapped the entire TFS project which had been mapped in a sub folder and not at the root.
Deleted files from disk completely
Remapped the TFS project, this time from the root TFS project level
Accepted the "get"
After doing this my build definitions loaded and worked. (Seems to be a mapping issue...bug...)
This may be an extream solution and I am still not sure what happened but it now works.
When starting VS 2012, I'm getting this error in the Output window:
> TF205020: Could not connect to server ‘https://Xxxxxxxx. This server was used in your last session, but it might be offline or unreachable. Confirm that the server is available on the network. To attempt to connect again, or to a different server, click ‘Connect To Team Foundation Server’ in Team Explorer or the Team menu.
>
> The server returned the following error: TF400324: Team Foundation
> services are not available from server https://Xxxxxxx. Technical
> information (for administrator): The underlying connection was
> closed: Could not establish trust relationship for the SSL/TLS secure
> channel.
(Xxxxx used for server name here).
This is a TFS server I used on a contract project a couple of months ago - I'm no longer working with them so I want it just gone. I removed the server in the Team / Connect to Team Foundation Server... dialog but this seems to live on in VS's memory somewhere.
Anyway to make it be gone/gone?
I (finally) was able to remove all my bindings and references to an old TFS server by doing the following:
Delete the contents of the folder, %LocalAppData%\Microsoft\TeamFoundation\Cache.
As someone else suggested, search for all occurrences of LocalItemExclusions.config within %LocalAppData%\Microsoft\Team Foundation\, and remove any/all "TeamProjectCollection" elements that reference the obsolete server in their uri="..." attribute.
Edit the file, %LocalAppData%\Roaming\Microsoft\VisualStudio\11.0\TeamExplorer\TeamExplorer.Config. Remove all "Server" elements having a url attribute that references the obsolete server.
I did this for both VS 2010 and VS2012. It was not until I completed the third step that the error mentioned by the original poster went away, and Visual Studio started quickly, as it always used to.
I was unwilling to use the nuclear option as described in the first part of superlime's answer to this question--deleting the entire contents of "%LocalAppData%\Microsoft\Team Foundation\".
Instead I followed the second part of his answer--deleting the contents of "%LocalAppData%\Microsoft\Team Foundation\N.N\Cache", which I did for all versions (N.N) found.
That helped, but wasn't quite enough. I also had to do the following:
Search for all occurrences of a file called LocalItemExclusions.config within "%LocalAppData%\Microsoft\Team Foundation\" and its subfolders.
Remove from those files, in their entirety, any <TeamProjectCollection> elements that reference the obsolete server in their uri="..." attribute.
That was enough for me--however, I can imagine other references lurking, if you've been using TFS targeting that server for awhile. If the above steps are insufficient, you might simply try searching for additional references in all files (excluding logs) in that directory hierarchy, and surgically removing them.
I found that I needed to do both steps to remove this from VS 2012 :
Delete the content of the folder %LocalAppData%\Microsoft\TeamFoundation\Cache
Delete the content of the folder %LocalAppData%\Microsoft\Team Foundation\
Much thanks to both contributors for their help. Shame to Microsoft for not insuring that removing Team Foundation occurs cleanly.
Bit of a "nuke from orbit" option, but try deleting the contents of the TFS client cache. Should be located in this location:
%LocalAppData%\Microsoft\Team Foundation\
According to this blog post (which is for 2010, and a little stale on version info), you should just delete the contents of the cache folder, not the cache folder itself (or the parent dir).. So theoretically you'd just want to delete everything inside of:
%LocalAppData%\Microsoft\Team Foundation\4.0\Cache
I am using Team Services on domain visualstudio.com and I need to delete one project, I found out that I need to use command prompt to delete projects, but when I tried the script it seemed that it doesn't work
My Script is,
TfsDeleteProject
/force collection:https://mytfs.visualstudio.com/DefaultCollection MyProject
My first mistake was that I didn't append DefaultCollection to the URL, but now I get error that I don't have privileges.
Thanks to #Christopher I was able to make the script work.
You can use the following command from the "Developer Command Prompt":
TfsDeleteProject /collection:https://mytfs.visualstudio.com/DefaultCollection MyProject
You can now do it via visualstudio.com
Open the administration context for the team project collection by choosing the gear icon.
Open the menu for the team project that you want to delete.
If you don’t see the actions icon , either you’re not accessing VSTS or you’re not a member of the Project Collection Administrators group.
You must type the name of the team project in order to initiate the delete operation.
Open “Developer Command Prompt” under “Program Files>Microsoft Visual Studio” or in Windows 8 type “Developer“.
In the command prompt, use this command template below to delete your project from TFS. Replace the YourTFSName to yours and also the ProjectName to the name of your project.
TfsDeleteProject /collection:https://YourTFSName.visualstudio.com/DefaultCollection ProjectName
Hit Enter and then Y if you are prompted for confirmation.
Done. Double check by login to your TFS online.
From http://bizvise.com/2013/03/08/how-to-delete-team-project-from-my-team-foundation-service-tfs-default-collections/
Although the accepted answer is absolutely correct and very clear, I managed to get lost and run into that 'grayed out Delete button' issue and just wanted to share what I was doing wrong.
For the folks having issue with grayed out delete button, make sure that you are inside 'View the collection administration page' (as shown in the accepted answer), not inside the project itself.
If the last breadcrumb on the top of your VS Team Services is the name of the project, you are at the wrong place (it looks similar). Here the Delete button (appears on right clicking the project name) will be grayed out.
If you click the link that says 'View the collection administration page' after clicking the Settings(gear), you will be at the right place.
if your project name have space, you must use "MyProject name"
TfsDeleteProject /collection:https://mytfs.visualstudio.com/DefaultCollection "MyProject name"
I've been developing a new SharePoint 2010 package in Visual Studio 2010. This is my first development project in SharePoint so please pardon my use of incorrect terminology.
Within the package/solution there are a couple of Features, a couple of custom web forms, and a workflow for the custom list type which is also within the solution.
To develop and debug I've been simply using the Build > Deploy Solution option from within Visual Studio to build the solution and then it would automatically connect to my sharepoint server and create the custom List, install the features, add the workflow, etc.
But when I want to make a change, say change the color of the text on the custom NewForm (mine is called MyCustomForm.ascx) then I click Build > Deploy Solution it deletes the custom list, deletes the workflow, deactivates and deletes the features and then re adds them all again. Thus I lose all of my list items.
In production if I need to modify the workflow I can't simply do this as we would lose all of our list items. How can I do this?
I've done days worth of research and nothing works. I've looked into:
stsadm -o upgradesolution -name SharePointProject1.wsp -filename ...
stsadm.exe -o execadmsvcjobs
with no avail. It says everything "works" fine (no errors) but doesn't update the custom MyCustomForm.
I've also tried manually editing the files in:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES
to no avail as well. I modify the MyCustomForm.ascx file and refresh the SharePoint site page and it hasn't changed.
Any insight would be helpful. I am doing all development on the server machine that is running SharePoint and have admin access if that helps. Thank you in advance for all of your help.
The list is deleted because the solution package that you're deploying has the list item in it so Visual Studio is "helping" by making sure that you get the lastest version of everything (even it it hasn't changed)
There are two approaches you can take to over-ride this behaviour
Set the deployment model to "No Activataion" this will result in the package being deployed and leaving previously deployed and activated feature in place.
Remove the list instance item from the package by double clicking on the Package in the Solution Explorer and then double clicking on the List Instance Item in the right hand pane.
Next time re-deploy the solution you not should have your existing list removed (I'm not 100% on the workflow association behaviour).
Of the two I'd lean towards option 2