-
Notifications
You must be signed in to change notification settings - Fork 448
Can't use local workspace #465
Comments
I am having the same issue. After fixing the authentication issue in 1.31 it now views all local workspaces as server workspaces. |
@erikread Does it work if you disable |
yes it does now. That didn't work last week for some reason. Hadn't tried it until today. Was in the process of getting WebStorm setup. |
Maybe post how to disable proxy support? BTW, that doesn't work for me. Still treats my local workspace as a server workspace. |
@jrichview Must be a different problem then. Has it worked at an earlier point? |
No, never has. Not with VSCode anyway. Works fine with VS2017 . Currently I do manual checkins/checkouts via the source code explorer in that. Also where I manage my workspace settings. |
It is absolutely ridiculous that this functionality still does not work. Trying to set my team up to use Visual Studio Code with Azure DevOps, which should work seamlessly, but I'm getting the same error I used to when I first set this up for myself a couple of years ago. I have a local workspace and VS Code thinks it's a server workspace. WHEN WILL THIS BE FIXED???!!! |
I can't use my local workspace with the extension. Looks good with the TEE CLC client and I can do basic stuff with the CLC. Nothing can be done in VSCode. I see Team (!) in the lower left corner of the VSCode window and captured the following log file.
The text was updated successfully, but these errors were encountered: