<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> P4Connection.Save_Form Method (P4Form) </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" > P4Connection.Save_FormMethod(P4Form) </h1> </div> </div> <div id = "nstext" > <p> Saves the form to Perforce. </p> <div class = "syntax" > <span class = "lang" > [VisualBasic] </span> <br /> OverloadsPublicFunctionSave_Form( _ <br /> ByVal <i> Form </i> As <a href = "P4API.P4Form.html" > P4Form </a> _ <br /> )As <a href = "P4API.P4UnParsedRecordSet.html" > P4UnParsedRecordSet </a></div> <div class = "syntax" > <span class = "lang" > [C#] </span> <br /> public <a href = "P4API.P4UnParsedRecordSet.html" > P4UnParsedRecordSet </a> Save_Form( <br /><a href = "P4API.P4Form.html" > P4Form </a><i> Form </i><br /> ); </div> <h4 class = "dtH4" > Parameters </h4> <dl> <dt> <i> Form </i> </dt> <dd> The P4Form object retrieved from Fetch_Form. </dd> </dl> <h4 class = "dtH4" > Return Value </h4> <p> P4UnParsedRecordSet. Output can be parsed to verify the form was processed correctly. </p> <h4 class = "dtH4" > Remarks </h4> <p> Forms are the things that pop-up in an editor when run from a command line. In P4.Net (and most other Perforce APIs), you do not need to parse/format the text manually. Instead, you can get/set the fields using the Fields and ArrayFields collections. <P> The following is a list of common form commands: </P> <list> <li> client </li> <li> branch </li> <li> label </li> <li> job </li> <li> user </li> <li> group </li> <li> protect </li> <li> triggers </li> <li> branch </li> </list> <P> When fetching or saving a form, <B> do not use the '-o' and '-i' flags </B> . P4.Net will automatically include them. </P> </p> <h4 class = "dtH4" > See Also </h4> <p> <a href = "P4API.P4Connection.html" > P4Connection Class </a> | <a href = "P4API.html" > P4API Namespace </a> | <a href = "P4API.P4Connection.Save_Form_overloads.html" > P4Connection.Save_Form Overload List </a></p> <object type = "application/x-oleobject" classid = "clsid:1e2a7bd0-dab9-11d0-b93a-00c04fc99f9e" viewastext = "true" style = " display : none ; " > <param name = "Keyword" value = "Save_Form method" > </param> <param name = "Keyword" value = "Save_Form method, P4Connection class" > </param> <param name = "Keyword" value = "P4Connection.Save_Form method" > </param> </object> <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
#3
7709
Shawn Hladky
P4.Net: Cleanup, documentation, and a a start for implementing an object-based outpu ... t for filelog. «
15 years ago
#2
6105
Shawn Hladky
P4.Net: Updating documentation output to sandcastle.
17 years ago
#1
5830
Shawn Hladky
P4.Net: reorg to support release branches
18 years ago
//guest/shawn_hladky/P4.Net/doc/html/P4API.P4Connection.Save_Form_overload_1.html
#1
5812
Shawn Hladky
P4.Net: More documentation.
18 years ago