Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

team.Reinitialize not found #221

Closed
tegaaa opened this issue May 5, 2017 · 9 comments
Closed

team.Reinitialize not found #221

tegaaa opened this issue May 5, 2017 · 9 comments

Comments

@tegaaa
Copy link

tegaaa commented May 5, 2017

This is still not working with latest code 1.12.1 and extension 1.117.3

@jeffyoung
Copy link
Contributor

Do you have a folder opened in VS Code before you run the commands? If not, I believe that's #204 (which I have a PR out to address). But the extension requires that a folder is open inside VS Code.

I've also cracked open the 117.3 VSIX and see the code I re-added in #206. Can you provide a screenshot of the status bar or the error message you're seeing?

@Rainson12
Copy link

if you are on windows, can you check if you are using double slashes in your settings.json? Like:
"tfvc.location": "C:\Program Files (x86)\TEE-CLC-14.114.0\tf.cmd",

happend to me..

@tegaaa
Copy link
Author

tegaaa commented May 9, 2017 via email

@tegaaa
Copy link
Author

tegaaa commented May 9, 2017 via email

@tegaaa
Copy link
Author

tegaaa commented May 15, 2017 via email

@jeffyoung
Copy link
Contributor

Can you turn on debug logging and see if there's any interesting information in the log (provide it here)?

I see that you're using TF.exe with a French VS Code so perhaps our detection of the TFVC workspace isn't perfect (TF.exe will, by default, output in French on an OS configured with French UI). If the extension detected French output, you'd be getting an error similar to It appears you have configured a non-English version of the TF executable. Please ensure an English version is properly configured. Having the output of a tf workfold command would also be helpful.

Also, what can you say about the differences between the two machines (working and non-working)? If you're using the CLC on one of them, the CLC is set to always return English strings in its output. With TF.exe, you have to "force" it by not allowing it to find the proper resources (see #180) since you cannot tell it otherwise. If you're not able to fool TF.exe, you'll need to use the CLC on Windows (for non-English OSes).

@tegaaa
Copy link
Author

tegaaa commented May 16, 2017 via email

@jeffyoung
Copy link
Contributor

Thanks @tegaaa. I'm glad you were able to figure out the issue.

I've got a story on our backlog to investigate how to make TF.exe work across languages since we have to parse the output from TF.exe to provide the functionality in VS Code. (TF.exe emits its output based on the language that's set up on the OS without a method to override it. The TEE CLC can be forced to emit English strings regardless of the OS settings and that's what we do in the extension.) This functionality will likely require an update to TF.exe itself so I don't know when we would get around to adding that support. That said, I certainly appreciate the feedback.

Another potential workaround could be to install the "Team Explorer 2017" version of Visual Studio 2017, use the TF.exe which ships with that SKU and configure it for English. Then, you can use that version with VS Code while maintaining French in your Enterprise version (which is what you're currently using). You can find the Team Explorer 2017 version on the Visual Studio Downloads page under the "Visual Studio 2017" section (which needs to be expanded first).

@tegaaa
Copy link
Author

tegaaa commented May 16, 2017 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants