VSCode, Perforce: “SOURCE CONTROL No source control providers registered.”
I'm using VSCode x64 on Win10 x64, and desire to use Perforce with it. I have a Perforce installation on the same machine that already works with both local and remote VS clients. I've installed and loaded the VSCode Perforce plugin from VSCode Marketplace. Activation Mode is set to "autodetect".
However, in the Source Control pane, VSCode shows "SOURCE CONTROL No source control providers registered."
I've found No source control providers registered on Mac and tried the disable-reload sequence described but problem still exists.
No 3-dot menu to "Switch SCM provider". Right now I've disabled all other extensions, Have tried re-installing the extension, as well as adding Perforce login settings to workspace "settings.json", and have put similar ".p4config" at workspace root, but to no avail.
Found Git missing in VSCode - no source control providers, not sure where I would set the equivalent to "git.path" nor what the path would be: to Perforce itself, or to the VSCode extension; not sure of the path to that extension.
Would appreciate any hints on how to get the VSCode Perforce plugin to register. Is the VSCode Perforce plugin known to work with x64 for both VSCode and Win10?
git visual-studio-code perforce registration vscode-settings
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
asked Nov 27 '18 at 19:55
netboyznetboyz
64
add a comment |
I'm using VSCode x64 on Win10 x64, and desire to use Perforce with it. I have a Perforce installation on the same machine that already works with both local and remote VS clients. I've installed and loaded the VSCode Perforce plugin from VSCode Marketplace. Activation Mode is set to "autodetect".
However, in the Source Control pane, VSCode shows "SOURCE CONTROL No source control providers registered."
I've found No source control providers registered on Mac and tried the disable-reload sequence described but problem still exists.
No 3-dot menu to "Switch SCM provider". Right now I've disabled all other extensions, Have tried re-installing the extension, as well as adding Perforce login settings to workspace "settings.json", and have put similar ".p4config" at workspace root, but to no avail.
Found Git missing in VSCode - no source control providers, not sure where I would set the equivalent to "git.path" nor what the path would be: to Perforce itself, or to the VSCode extension; not sure of the path to that extension.
Would appreciate any hints on how to get the VSCode Perforce plugin to register. Is the VSCode Perforce plugin known to work with x64 for both VSCode and Win10?
git visual-studio-code perforce registration vscode-settings
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
asked Nov 27 '18 at 19:55
netboyznetboyz
64
Got it. .p4config in the project directory did it. Then open workspace and project folder. Thanks.
– netboyz
Nov 28 '18 at 21:28
...and I was able to delete the .p4config file by putting overrides for the same info plus a few config items into my user settings file.
– netboyz
Dec 3 '18 at 0:18
The above answer is correct but keep in mind which version of git you are using. In msys64/mingw under Windows you can't use the msys version of git but you must install the Windows version specifically or it will fail with this problem even if it is on the PATH!
– user2715390
Jan 28 at 6:10
add a comment |
I'm using VSCode x64 on Win10 x64, and desire to use Perforce with it. I have a Perforce installation on the same machine that already works with both local and remote VS clients. I've installed and loaded the VSCode Perforce plugin from VSCode Marketplace. Activation Mode is set to "autodetect".
However, in the Source Control pane, VSCode shows "SOURCE CONTROL No source control providers registered."
I've found No source control providers registered on Mac and tried the disable-reload sequence described but problem still exists.
No 3-dot menu to "Switch SCM provider". Right now I've disabled all other extensions, Have tried re-installing the extension, as well as adding Perforce login settings to workspace "settings.json", and have put similar ".p4config" at workspace root, but to no avail.
Found Git missing in VSCode - no source control providers, not sure where I would set the equivalent to "git.path" nor what the path would be: to Perforce itself, or to the VSCode extension; not sure of the path to that extension.
Would appreciate any hints on how to get the VSCode Perforce plugin to register. Is the VSCode Perforce plugin known to work with x64 for both VSCode and Win10?
git visual-studio-code perforce registration vscode-settings
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
asked Nov 27 '18 at 19:55
netboyznetboyz
64
I'm using VSCode x64 on Win10 x64, and desire to use Perforce with it. I have a Perforce installation on the same machine that already works with both local and remote VS clients. I've installed and loaded the VSCode Perforce plugin from VSCode Marketplace. Activation Mode is set to "autodetect".
However, in the Source Control pane, VSCode shows "SOURCE CONTROL No source control providers registered."
I've found No source control providers registered on Mac and tried the disable-reload sequence described but problem still exists.
No 3-dot menu to "Switch SCM provider". Right now I've disabled all other extensions, Have tried re-installing the extension, as well as adding Perforce login settings to workspace "settings.json", and have put similar ".p4config" at workspace root, but to no avail.
Found Git missing in VSCode - no source control providers, not sure where I would set the equivalent to "git.path" nor what the path would be: to Perforce itself, or to the VSCode extension; not sure of the path to that extension.
Would appreciate any hints on how to get the VSCode Perforce plugin to register. Is the VSCode Perforce plugin known to work with x64 for both VSCode and Win10?
git visual-studio-code perforce registration vscode-settings
git visual-studio-code perforce registration vscode-settings
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
asked Nov 27 '18 at 19:55
netboyznetboyz
64
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
asked Nov 27 '18 at 19:55
netboyznetboyz
64
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
edited Dec 3 '18 at 0:41
Kiran Vedula
17511
17511
asked Nov 27 '18 at 19:55
netboyznetboyz
64
asked Nov 27 '18 at 19:55
netboyznetboyz
64
asked Nov 27 '18 at 19:55
netboyznetboyz
64
64
Got it. .p4config in the project directory did it. Then open workspace and project folder. Thanks.
– netboyz
Nov 28 '18 at 21:28
...and I was able to delete the .p4config file by putting overrides for the same info plus a few config items into my user settings file.
– netboyz
Dec 3 '18 at 0:18
The above answer is correct but keep in mind which version of git you are using. In msys64/mingw under Windows you can't use the msys version of git but you must install the Windows version specifically or it will fail with this problem even if it is on the PATH!
– user2715390
Jan 28 at 6:10
add a comment |
Got it. .p4config in the project directory did it. Then open workspace and project folder. Thanks.
– netboyz
Nov 28 '18 at 21:28
...and I was able to delete the .p4config file by putting overrides for the same info plus a few config items into my user settings file.
– netboyz
Dec 3 '18 at 0:18
The above answer is correct but keep in mind which version of git you are using. In msys64/mingw under Windows you can't use the msys version of git but you must install the Windows version specifically or it will fail with this problem even if it is on the PATH!
– user2715390
Jan 28 at 6:10
Got it. .p4config in the project directory did it. Then open workspace and project folder. Thanks.
– netboyz
Nov 28 '18 at 21:28
Got it. .p4config in the project directory did it. Then open workspace and project folder. Thanks.
– netboyz
Nov 28 '18 at 21:28
...and I was able to delete the .p4config file by putting overrides for the same info plus a few config items into my user settings file.
– netboyz
Dec 3 '18 at 0:18
...and I was able to delete the .p4config file by putting overrides for the same info plus a few config items into my user settings file.
– netboyz
Dec 3 '18 at 0:18
The above answer is correct but keep in mind which version of git you are using. In msys64/mingw under Windows you can't use the msys version of git but you must install the Windows version specifically or it will fail with this problem even if it is on the PATH!
– user2715390
Jan 28 at 6:10
The above answer is correct but keep in mind which version of git you are using. In msys64/mingw under Windows you can't use the msys version of git but you must install the Windows version specifically or it will fail with this problem even if it is on the PATH!
– user2715390
Jan 28 at 6:10
add a comment |
1 Answer
1
active
oldest
votes
Following are steps to resolve "No source control providers registered" issue
1) Install GIT
2) Ensure GIT is added to Path environment variable, you can verify whether GIT installation by typing "CTRL+SHFT+P" in VS Code and entering "GIT: Show Git Output". Refer to the screenshot below
3) Visual studio code expects that a GIT repository is loaded into it by using open folder. You need to manually clone your GIT repository and load it into Visual studio using "Open Folder" from file menu or side bar
4)Now in your Source Control tab, you will find GIT successfully integrated
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
Thank you. That gets me to GIT which is good. I have stuff also from earlier projects that is in Perforce and had to get to that as well. But that's all working now... So I'm good for now. I appreciate your advice.
– netboyz
Dec 3 '18 at 0:17
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53507167%2fvscode-perforce-source-control-no-source-control-providers-registered%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Following are steps to resolve "No source control providers registered" issue
1) Install GIT
2) Ensure GIT is added to Path environment variable, you can verify whether GIT installation by typing "CTRL+SHFT+P" in VS Code and entering "GIT: Show Git Output". Refer to the screenshot below
3) Visual studio code expects that a GIT repository is loaded into it by using open folder. You need to manually clone your GIT repository and load it into Visual studio using "Open Folder" from file menu or side bar
4)Now in your Source Control tab, you will find GIT successfully integrated
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
Thank you. That gets me to GIT which is good. I have stuff also from earlier projects that is in Perforce and had to get to that as well. But that's all working now... So I'm good for now. I appreciate your advice.
– netboyz
Dec 3 '18 at 0:17
add a comment |
Following are steps to resolve "No source control providers registered" issue
1) Install GIT
2) Ensure GIT is added to Path environment variable, you can verify whether GIT installation by typing "CTRL+SHFT+P" in VS Code and entering "GIT: Show Git Output". Refer to the screenshot below
3) Visual studio code expects that a GIT repository is loaded into it by using open folder. You need to manually clone your GIT repository and load it into Visual studio using "Open Folder" from file menu or side bar
4)Now in your Source Control tab, you will find GIT successfully integrated
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
Thank you. That gets me to GIT which is good. I have stuff also from earlier projects that is in Perforce and had to get to that as well. But that's all working now... So I'm good for now. I appreciate your advice.
– netboyz
Dec 3 '18 at 0:17
add a comment |
Following are steps to resolve "No source control providers registered" issue
1) Install GIT
2) Ensure GIT is added to Path environment variable, you can verify whether GIT installation by typing "CTRL+SHFT+P" in VS Code and entering "GIT: Show Git Output". Refer to the screenshot below
3) Visual studio code expects that a GIT repository is loaded into it by using open folder. You need to manually clone your GIT repository and load it into Visual studio using "Open Folder" from file menu or side bar
4)Now in your Source Control tab, you will find GIT successfully integrated
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
Following are steps to resolve "No source control providers registered" issue
1) Install GIT
2) Ensure GIT is added to Path environment variable, you can verify whether GIT installation by typing "CTRL+SHFT+P" in VS Code and entering "GIT: Show Git Output". Refer to the screenshot below
3) Visual studio code expects that a GIT repository is loaded into it by using open folder. You need to manually clone your GIT repository and load it into Visual studio using "Open Folder" from file menu or side bar
4)Now in your Source Control tab, you will find GIT successfully integrated
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
answered Dec 1 '18 at 17:41
Kiran VedulaKiran Vedula
17511
17511
Thank you. That gets me to GIT which is good. I have stuff also from earlier projects that is in Perforce and had to get to that as well. But that's all working now... So I'm good for now. I appreciate your advice.
– netboyz
Dec 3 '18 at 0:17
add a comment |
Thank you. That gets me to GIT which is good. I have stuff also from earlier projects that is in Perforce and had to get to that as well. But that's all working now... So I'm good for now. I appreciate your advice.
– netboyz
Dec 3 '18 at 0:17
Thank you. That gets me to GIT which is good. I have stuff also from earlier projects that is in Perforce and had to get to that as well. But that's all working now... So I'm good for now. I appreciate your advice.
– netboyz
Dec 3 '18 at 0:17
Thank you. That gets me to GIT which is good. I have stuff also from earlier projects that is in Perforce and had to get to that as well. But that's all working now... So I'm good for now. I appreciate your advice.
– netboyz
Dec 3 '18 at 0:17
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53507167%2fvscode-perforce-source-control-no-source-control-providers-registered%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Got it. .p4config in the project directory did it. Then open workspace and project folder. Thanks.
– netboyz
Nov 28 '18 at 21:28
...and I was able to delete the .p4config file by putting overrides for the same info plus a few config items into my user settings file.
– netboyz
Dec 3 '18 at 0:18
The above answer is correct but keep in mind which version of git you are using. In msys64/mingw under Windows you can't use the msys version of git but you must install the Windows version specifically or it will fail with this problem even if it is on the PATH!
– user2715390
Jan 28 at 6:10