job000426
Open
When connecting, one can specify either (A) the current working directory or (B) the [port, client, user, password] quadruple, but not both.
As a result, it's not currently possible to implement the equivalent of the following command-line using P4API.NET:
set P4CONFIG=p4config.txt
echo P4USER=bdylan > /some/path/p4config.txt
p4 -d /some/path -c myClient [COMMAND]
which would result in:
* P4USER = bdylan (set via P4CONFIG)
* P4CLIENT = myClient (set via command-line switch)
See https://swarm.workshop.perforce.com/files/guest/perforce_software/p4api.net/p4api.net/Connection.cs method Connect(), the "if" block starting at line 223.
In P4API.NET, I can call:
(A) Connection.Connect(new Options { "cwd" : "/some/path" }) in which case I'll run with the CurrentWorkingDirectory set to /some/path, will find the p4config.txt file in that directory, and will set P4USER to bdylan. I can't specify the client/user/password unless I put them into the config file. (This uses the 1-parameter P4Server constructor.)
(B) Connection.Connect(null) in which case I'll make use of the Server/UserName/Client that I've set up. However, in this case I won't find p4config.txt. (This uses the 4-parameter P4Server constructor.)
It would be nice to allow utilising both (A) the "cwd" and (B) the Server/UserName/Client properties. In fact, there already is a 5-parameter P4Server constructor that could be used for this so this may not be too complicated...
As a result, it's not currently possible to implement the equivalent of the following command-line using P4API.NET:
set P4CONFIG=p4config.txt
echo P4USER=bdylan > /some/path/p4config.txt
p4 -d /some/path -c myClient [COMMAND]
which would result in:
* P4USER = bdylan (set via P4CONFIG)
* P4CLIENT = myClient (set via command-line switch)
See https://swarm.workshop.perforce.com/files/guest/perforce_software/p4api.net/p4api.net/Connection.cs method Connect(), the "if" block starting at line 223.
In P4API.NET, I can call:
(A) Connection.Connect(new Options { "cwd" : "/some/path" }) in which case I'll run with the CurrentWorkingDirectory set to /some/path, will find the p4config.txt file in that directory, and will set P4USER to bdylan. I can't specify the client/user/password unless I put them into the config file. (This uses the 1-parameter P4Server constructor.)
(B) Connection.Connect(null) in which case I'll make use of the Server/UserName/Client that I've set up. However, in this case I won't find p4config.txt. (This uses the 4-parameter P4Server constructor.)
It would be nice to allow utilising both (A) the "cwd" and (B) the Server/UserName/Client properties. In fact, there already is a 5-parameter P4Server constructor that could be used for this so this may not be too complicated...
- Status
- Open
- Project
- perforce-software-p4api-net
- Severity
- C
- Reported By
- QAP
- Reported Date
- 9 years ago
- Modified By
- Perforce maintenance
- Modified Date
- 6 years ago
- Owned By
- QAP
- Type
- Feature
Log in to comment