I renamed my computer name, and now my TFS workspace is broken in Visual Studio 2012.
When I type:
tf workspaces /computer:ABOTONJIC-PC /owner:* /format:detailed
Workspace : ABOTONJIC-PC
Owner : wrongowner#test.com
Computer : ABOTONJIC-PC
Comment :
Collection : netuse.visualstudio.com\DefaultCollection
Permissions: Private
Location : Local
File Time : Current
But I need to have :
Owner : realowner#test.com
Computer : NEW-PC
Then I try:
tf workspaces /updateComputerName:ABOTONJIC-PC /collection:netuse.visualstudio.com/DefaultCollection
No workspace matching *;wrongowner#test.com on computer NEW-PC found in Team Foundation Server netuse.visualstudio.com/DefaultCollection.
So my question are :
How to update computer name in my workspace?
Why TFS still shows "wrongowner#test.com" in workspace although there is new email registered as "realowner#test.com"?
Install Team Foundation Sidekicks. It's free.
Open the Workspace Sidekick, click Search, and select your workspace from the list.
Click the blue computer icon to Update Workspace Computer Name and you're done.
I installed Sidekicks. It did not work for this issue, but this did:
C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE>tf workspaces /updateComputerName:OldComputerName /s:"https://tfsServerName"
I had the same issue, also a VisualStudio.com account.
I've tried what the prompt told me :
Like so :
tf workspaces /updateComputerName:MyOldComputerName
but I got back :
The /collection option must be specified whenever /updateComputerName
or /updateUserName is specified.
In order to get the collection name I ran :
tf workspaces
which listed my collections and I got the name of my collection (...myusername.visualstudio.com...)
Then I ran :
tf workspaces /collection:http://myusername.visualstudio.com /updateComputerName:MyOldComputerName
Didn't work as I got this:
TF31002: Unable to connect to this Team Foundation Server:
http://myusername.visuals tudio.com/defaultcollection. Team Foundation
Server Url: http://myusername.visualstudio.com/defaultcollection.
Possible reasons for failure include:
- The name, port number, or protocol for the Team Foundation Server is incorrect
- The Team Foundation Server is offline.
- The password has expired or is incorrect.
Technical information (for administrator): The remote server returned
an error: (404) Not Found.
Then I noticed that I've typed http instead of https, corrected, retried and it worked!
In
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE>
run in CMD as admin this command
tf workspaces /collection:https://SERVER_NAME.visualstudio.com/DefaultCollection /updateComputerName:OLD_COMPUTER_NAME
To get this to work in Visual Studio 2017 use the following (new location)
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\TF.exe workspaces /collection:https://youraccountnamehere.visualstudio.com /updateComputerName:OLD-COMPUTERNAME
Hope this saves someone some time!
Look at this link
Vaccano said :
This command did the trick:
tf workspaces /updateComputerName:MyOldComputerName
/s:"http://MyServer:8080/tfs/MyCollection"
It had to be run from the computer I wanted to assign the workspace to (that is how it gets the new computer name.
>
tf workspaces /updateComputerName:REPLCATEOLDCOMPUTERNAMEHERE /collection:REPLACETFSURL
example:
tf workspaces /updateComputerName:DESKTOP-42CLO97 /collection:https://testuserxx.visualstudio.com
VS2017
Open Command prompt and type as shown in below
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE
and type the following code with your credential
tf workspaces /updateComputerName:OldComputerName
/s:"https://tfsServerName"
In CMD prompt
C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE>tf
workspaces
/updateComputerName:OldComputerName/s:"https://tfsServerName"
You can add new workspace then use vs 2017 delete your previous workspace:
What worked for me was typing
tf workspaces /updateComputerName:MyOldComputerName /collection:"anything".visualstudios.com/DefaultCollection/
Open the visual studio command prompt and type the following command
tf workspaces /updateComputerName:oldcomputername /s:http://tfservername:port#/tfs
for example
tf workspaces /updateComputerName:abc-PC /s:http://mytfsserver:8080/tfs
You can run the following command before and after running the above command, this is just to check the workspaces information on your computer.
Remember: run all these commands on client computer (which is renamed) and not on the computer where TFS server is installed.
If user name is also changed then run the following command
tf workspaces /updateUserName:oldUserName /s:http://mytfsserver:8080/tfs
Hope it will help.
Related
When I try to instantiate a VFP COM (OlePublic) DLL from my .NET web app running in IIS on Windows server 2016 I get:
Retrieving the COM class factory for component with CLSID {A55C4127-DDCB-4E5F-B69C-A7EAC83A83DC} failed due to the following error: 80004005 Unspecified error (Exception from HRESULT: 0x80004005 (E_FAIL)).
I was able to track it down (using Simon's comment) to it not being able to find vfp9r.dll:
Those files got installed w/ my InstallShield package under C:\Program Files (x86)\Common Files\Microsoft Shared\VFP:
vfp9r.dll
VFP9RENU.dll
vfp9t.dll
Why isn't "it" searching that dir? I got one server it is finding them under program files and another that isn't. How does that magic work?
update
if I install VFP 9, it will search that dir & successfully load it. So what is the VFP 9 install doing to my machine to tell "it" to search that dir not just the current dir & \SysWow64? 🤔
workaround
import these registry keys:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\VisualFoxProRuntimeMT.9\Shell\Open\Command]
#="C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\VFP\\vfp9t.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\VisualFoxProRuntime.9\Shell\Open\Command]
#="C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\VFP\\vfp9r.dll"
(save the above 'script' as a .reg file and double click it to import it)
how I figured this out:
Hyper-V checkpoints so I could quickly go back and forth from a working to a non-working vm along w/ resetting after I did some test to find the minimal workaround
Search & export registry key w/ vfp9r.dll or vfp9t.dll
Compare exports via Notepad++ Compare Plus Plugin
The diff for vfp9t.dll was smaller so that was helpful. I grabbed the first key and that worked. Then I searched for the same-ish path for the vfp9r.dll export and grabbed that key.
According to https://developer.android.com/topic/performance/reduce-apk-size, I should be able to install Android Size Analyzer as a plugin, but nothing shows up.
Android Studio -> File -> Settings -> Plugin -> Marketplace -> search for "Android Size Analyzer"
UPDATE: 17th May 2022
After a lot of trials, errors & frustration, I was able to make it work. Here are the steps: (for MacOS)
Download the the plugin's zip folder from the Github https://github.com/android/size-analyzer/releases
Extract the zip and add the size-analyzer executable and the analyzer.jar to Users/<your_user>/Library/Android/platform-tools
(You can add the above files to any place but I bundled it with platform-tools because this location was already present in my $PATH variable. Wherever you place those two files, please make sure that this location is present in your $PATH variable else it won't work. Don't know how to set path variables? Please refer this https://techpp.com/2021/09/08/set-path-variable-in-macos-guide)
Now in your Android Studio Terminal, run the following command
size-analyzer check-project <your-path-to-project-directory>
(After above step, If the terminal complains like size-analyzer command not found, it means your $PATH variable is not set properly)
After analyzing the entire project, it shows output like this
The result analysis provides lots of suggestions and space saving options. Thank you Google for such amazing plugin : )
=================
OLD : 16th May 2022
The AS plugin Android Size Analyzer is deprecated! It's no more indexed on Plugin Market Place(You cannot install it directly from AS anymore).
I even tried installing the plugin from their GitHub Repo, but all in vain. When adding the plugin to studio from disk, the following error popped up.
Maybe you can try downgrading the studio and then install it.
Looks like, we'll be on our own for a while : (
I am trying to clone a github repository from my account in my Android studio, but each time I try to clone it by
VCS -> get from version control -> URL, an error message pops up with message:
"Clone: Unable to create destination directory".
What can I do?
Go to your Android Studio installation directory (usually Program Files/Android/Android Studio).
Go to the bin folder.
Right click studio64.exe (or studio.exe if you're using the 32bit
version) and run it as an administrator.
Now clone should work just fine.
I'm sure there is a better solution out there but right now, this should work.
Check your folder path.
In my case, my directory name had whitespace, so I changed the folder name from namu nikam to namunikam.
After that, github cloned the project.
The project error message was:
Cmd doesn't allow us to run commands with any space in between
Sometimes we use underscores between words, like namu_nikam.
I want VS let me use remote debbuging on Linux machine. I have downloaded necccessary packages and tools for this goal, so, I've denoted output and build directories. Build directory is created always successfully, but next step is Makefile that is not run, because CMakeList.txt is not sent from Windows machine.
I text in Additional Sources To Copy that this file should be copied, but I cannot know a reason of unsuccessful action. Only make command notifies me that this file does not exist. I guess this problem is in Visual Studio!
I have solved the problem and totally sure, that these things will exactly help you out!
https://developercommunity.visualstudio.com/content/problem/447310/2019-makefile-project-doesnt-copy-source-on-build.html
Fix the file
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VC\VCTargets\Application Type\Linux\1.0\Linux.Makefile.targets
243 line, add this:
<Target Name="PrepareForNMakeBuild" DependsOnTargets="SetBuildDefaultEnvironmentVariables;SetUserMacroEnvironmentVariables;_RequiresRemoteConnection;_CopySources;">
Never use '~' when you denote pathes on remote machine in properties of debbuging, only like
/home/machine_name/project_name/$(SolutionName)/$(USERNAME)
I tried to use unshelve /migrate command of tfpt to move the shelves of one branch to another. I have used the command which is given below,
tfpt unshelve /migrate /source:"$/Project name/branch name" /target:"$/Project name/branch name" "shelvesetname"
But gives the error as "Unable to determine the workspace"
Is there any solution for this?
Can anyone give the examples of how to give target and source paths?
How to do unshelve with migrate in Visual studio 2012 interface ?
Are both branches mapped in a workspace on your local machine?
If not, map them.
If so, are you running the command from within the workspace?
i.e. "$/Project name/branch name" is mapped to "C:\TFS\Project Name\branch name"
so run the command from "C:\TFS\Project Name\branch name"
Finally you could try running tf workspaces before running the command