Not working for Visual Studio 64 bit release

[miguelofbc]

Hi,

First of all, thank you very much for this extension. It's very helpfull!

I was using it for 32 bit visual studio version, and everything was working perfectly. I had a .p4config in my workspace home directory and after login everything was working.

After the update to 64 bit version the extension is not starting. I cannot see anything in SOURCE CONTROL.

Thanks, Miguel Oliveira

[miguelofbc]

The issue in my case is that the extension cannot perform the login.

It may not be related with 64 bit version, I just recall that I've changed my perforce password. But even when I do login with the new password it's not working. I am always getting the following message:

Password must be set before access can be granted.

How can I fix that? Is it a confict between the previous password and the new password? If so, how can I clear the previous password?

Thanks, Miguel Oliveira

[stef-levesque]

I've been testing with the 64bit version for along time now, this is unlikely to come from there. Double-check your settings in the .p4config file. Otherwise, try to set your informations in your user config, as shown in README.md

[ericgross2]

I seem to have the same issue:

Stock VS Code 1.26.1 x64 install (user) Latest Perforce P4V+command line install

Installed p4 extension and don't see anything listed in SCM providers.

Set user/workspace info in user config with no changes in behavior.

[ulfwin]

@ericgrossNI: I have to set activation mode to "always", otherwise it never starts, no matter if I create a .p4config file or use the vs code settings. Perhaps you're having the same problem as me?

[ericgross2]

@ulfwin cool! how do I do that?

[ulfwin]

@ericgrossNI: There is a setting for the extension called "perforce.activationMode". It's explained in more detail at the marketplace: https://marketplace.visualstudio.com/items?itemName=slevesque.perforce

[ericgross2]

@ulfwin Thanks! That was it! Now it is working.

[ulfwin]

@ericgrossNI: In fact, I just found out what my issue was before... turns out I need to set an environmental variable called P4CONFIG with value .p4config and then place a file with that name under the root of the workspace (aka client). More info can be found here . I've changed back to "autodetect" and it works now :) So not a problem in the extension, but it would help if it was mentioned in the readme.