Helix SwarmHelix Swarm

KnownIssues.html

  • //
  • guest/
  • erik_purins/
  • P4.Net/
  • main/
  • doc/
  • KnownIssues.html #1
  • View
  • Commits
  • Open Download .zip Download (4 KB) 
  1. <html dir="LTR">
  2.   <head>
  3.     <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" />
  4.     <meta name="vs_targetSchema" content="http://schemas.microsoft.com/intellisense/ie5" />
  5.     <title>P4Record Class</title>
  6.     <xml>
  7.     </xml>
  8.     <link rel="stylesheet" type="text/css" href="MSDN.css" />
  9.   </head>
  10.   <body id="bodyID" class="dtBODY">
  11.     <div id="nsbanner">
  12. 	<div id="bannerrow1">
  13. 		<table class="bannerparthead" cellspacing="0" id="Table1">
  14. 			<tr id="hdr">
  15. 				<td class="runninghead">Perforce API for the .Net CLR</td>
  16. 				<td class="product"><img alt="P4.Net" src="p4net.GIF" /></td>
  17. 			</tr>
  18. 		</table>
  19. 	</div>
  20. 	<div id="TitleRow">
  21. 		<h1 class="dtH1">Known Limitations</h1>
  22. </div>
  23. </div>
  24.     <div id="nstext">
  25.       <H4 class="dtH4">Internationalized Servers</H4>
  26.       <P>Perforce servers running in "unicode" or "internationalized" are unsupported.<P/>
  27.       I would like to have this fixed for v1.0, but unfortunately there are some major changes that need
  28.       to happen.  My plan is to fix this for 2.0, and therefore will only run on the 2.0 Framework.
  29.       </P>
  30.       <h4 class="dtH4">Forms</h4>
  31.       <P>Direct manipulation of the form text is not supported.  That is, there is no
  32.       way get the raw text of a form command or to save a form with the raw text.  Instead,
  33.       you must use the P4Form object.
  34.       </P>
  35.       <h4 class="dtH4">p4 print</h4>
  36.       <P>There is currently no way to obtain an in-memory stream of file contents using the 'print'
  37.       command.  In other APIs, if multiple files are output using 'print', the contents of the file
  38.       are concatenated into one in-memory variable.  I have an idea that would correct this behavior,
  39.       but it is more complex to consume.  So I've punted on the idea for now, and it is unsupported.
  40.       </P>
  41.       <h4 class="dtH4">p4 filelog</h4>
  42.       <P>The parsed output for the of the filelog command is awkward.  In the native C++ api, the
  43.       integration metadata is a sparse 2 dimensional array.  The parsing logic in P4.Net does not
  44.       account for this, so you end up with an ArrayFieldDictionary with keys like 'fromFile1,'.
  45.       So, I could fix this, and come up with some sort of TwoDimArrayFieldDictionary.  However,
  46.       the trying to make sense of the filelog output using the 2-d arrays will almost certainly
  47.       give you a headache.  Instead, I want to research Tony Smith's implementation in P4Ruby.  He
  48.       has created an object model that represents the filelog metadata in an easy-to-use interface.
  49.       </P>
  50.       <h4 class="dtH4">Submitting Default Changelist</h4>
  51.       <P>In P4.Net, theres no straight-forward way to submit the default pending changelist.
  52.       This is by design. If the client workspace has opened files in the default changelist
  53.        before any P4.Net automation runs, those files will "come along for the ride" when
  54.        you submit the default changelist. If the user has a JobView set, all jobs in that
  55.        JobView will automatically be fixed when you submit that default changelist. Both
  56.        of those behaviors are almost never desired, and Ive found many scripts that have
  57.        those bugs.
  58.        </P>
  59.        <P>
  60.        Note, starting in 2006.2, Perforce has native support for automatically submitting the
  61.        default changelist.  This is accomplished with: p4 submit -d "change description".  I caution it's usage,
  62.        as it has the same limitations decribed above.
  63.       </P>
  64.       <h4 class="dtH4">Changing Port after Connected</h4>
  65.       <P>You can not change the P4Port setting after a P4Connection has been connected.
  66.       This is true even after a Disconnect().  Instead, create a new P4Connection object.
  67.       </P>
  68.       <h4 class="dtH4">Supported Server Versions</h4>
  69.       <P>Servers lower than 2004.2 begin to fail the unit tests.  However, it is not a complete failure.
  70.       One issue is the use of p4 login.  The other failure is in the ConvertDate methods, because they
  71.       use p4 info in parsed mode to determine the server's time zone.  If you avoid those methods, P4.Net
  72.       should work fine against older servers.
  73.       </P>
  74.       <hr />    <div id="footer">
  75.         <p>
  76.           <a href="Copyright.html">Copyright  2006 Shawn Hladky</a>
  77.         </p>
  78.         <p>
  79.         </p>
  80.       </div>
  81.     </div>
  82.   </body>
  83. </html>
# Change User Description Committed
#1 7341 Erik Purins p4.net
---
pull p4.net#head 		16 years ago
//guest/shawn_hladky/P4.Net/main/doc/KnownIssues.html
#1 5830 Shawn Hladky P4.Net: reorg to support release branches 18 years ago
//guest/shawn_hladky/P4.Net/doc/KnownIssues.html
#4 5824 Shawn Hladky P4.Net: Last bits of documentation for 0.9 18 years ago
#3 5815 Shawn Hladky P4.Net: more documentation
will build strong-named assemblies now. 		18 years ago
#2 5812 Shawn Hladky P4.Net: More documentation. 18 years ago
#1 5798 Shawn Hladky P4.Net...  still not ready for beta
Added license to all files
Added several doc fi...les
Misc bugs «		 18 years ago