<html dir="LTR"> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" /> <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5" /> <title>P4.Net Overview</title> <xml> </xml> <link rel="stylesheet" type="text/css" href="MSDN.css" /> </head> <body id="bodyID" class="dtBODY"> <div id="nsbanner"> <div id="bannerrow1"> <table class="bannerparthead" cellspacing="0" id="Table1"> <tr id="hdr"> <td class="runninghead"> Perforce API for the .Net CLR</td> <td class="product"> <img alt="P4.Net" src="p4net.GIF" /></td> </tr> </table> </div> <div id="TitleRow"> <h1 class="dtH1"> Sample Applications</h1> </div> </div> <div id="nstext"> <h4 class="dtH4"> Job Labeler</h4> <p> Job labeler is a Windows service that polls the Peforce server for new job fixes, and creates a label representing the files fixed by a job.</p> <p> Motivation: Many shops use jobs to organize a collection of changes. For example, if you have Perforce integrated with a defect tracking system, you will have a job representing a defect, and there may be several changes fixed by that job. A frequent question that comes up is, "What files were modified to fix this defect?" Since the JobLabeler sample application creates a label representing the files fixed by a job, this question is readilly answered with "p4 files @={joblabel}". </p> <p> Techniques: Even if you don't use jobs in this manner (or jobs at all), there are a number of techniques that may be used in your applications. <list> <li>Using P4.Net from a Windows service</li> <li>Polling the Perforce server for change.</li> <li>Reading/Writing counters to maintain state.</li> <li>Using parsed and unparsed output of several commands.</li> <li>Fetching/Setting p4 settings from an app.config file.</li> </list> </p> <hr /> <div id="footer"> <p> <a href="Copyright.html">Copyright 2006 Shawn Hladky</a> </p> <p> </p> </div> </div> </body> </html>
# | Change | User | Description | Committed | |
---|---|---|---|---|---|
#5 | 5830 | Shawn Hladky | P4.Net: reorg to support release branches | ||
#4 | 5824 | Shawn Hladky | P4.Net: Last bits of documentation for 0.9 | ||
#3 | 5815 | Shawn Hladky |
P4.Net: more documentation will build strong-named assemblies now. |
||
#2 | 5812 | Shawn Hladky | P4.Net: More documentation. | ||
#1 | 5798 | Shawn Hladky |
P4.Net... still not ready for beta Added license to all files Added several doc files Misc bugs |