# The form data below was edited by norman_morse
# Perforce Workshop Jobs
#
#  Job:           The job name. 'new' generates a sequenced job number.
#  Status:        Job status; [open/closed/suspended].  Required
#  Project:       The project this job is for. Required.
#  Severity:      [A/B/C] (A is highest)  Required.
#  ReportedBy     The user who created the job. Can be changed.
#  ReportedDate:  The date the job was created.  Automatic.
#  ModifiedBy:    The user who last modified this job. Automatic.
#  ModifiedDate:  The date this job was last modified. Automatic.
#  OwnedBy:       The owner, responsible for doing the job. Optional.
#  Description:   Description of the job.  Required.
#  DevNotes:      Developer's comments.  Optional.
#  Type:	  Type of job; [Bug/Feature].  Required.

Job:	job000196

Status:	open

Project:	perforce-software-p4api-net

Severity:	B

ReportedBy:	norman_morse

ReportedDate:	2015/04/07 09:31:00

ModifiedBy:	norman_morse

ModifiedDate:	2015/04/07 09:31:00

Description:
	p4api.net creates inconsistent signatures if user has passed in ProgramName and ProgramVer options.
	
	When reviewing p4api.net activities in the Perforce Log I was getting inconsistent signatures.
	
	Several initialization calls do not use the passed in options, this was fixed in P4Connect by moving the 
	option parsing code to earlier in the Connection sequence.
	
	Diffs can be found in the p4connect project under swarm, look at:
	
	//guest/norman_morse/dev/p4connect/src/P4Bridge/p4api.net/Connection.cs#4 and compare it to the previous revision.

DevNotes:

Type:	Bug