EngineV2 None;Black;2;Solid;False;4;Black Transparent All;Black;1;Solid;False;4;Black Transparent 0,0.4,19,0.4 Transparent True 0,0,19,0.4 Arial,8 Center 0,0,0,0 Text1 The first entry (Standard) prints using more lines than it should, and results in cut-off text. But the 2nd (WYSIWYG) prints in _fewer_ lines than it should, resulting in extra space. The last is Typographic, and appears "just right". Black HotkeyPrefix=None, LineLimit=False, RightToLeft=False, Trimming=None, WordWrap=True, Angle=0, FirstTabOffset=40, DistanceBetweenTabs=20, Expression PageHeader1 All;Black;1;Solid;False;4;Black Transparent 0,1.6,19,0.4 [210:234:240] True 0.2,0,18.8,0.4 Arial,8 d6c82ddb104343d98a3aea7fed62fdd6 0,0,0,0 Text2 Say you are running tests in your team builds, and you have configured your build so they can run on a Developer desktop as well as on a build server. By default, using Microsoft’s targets, tests are not run during a Desktop Build. This means that a build can pass when run locally but fail, or give partial success on the server, due to test errors. We had a scenario where some tests were “Not runnable” in our Test Container. Which resulted in failed builds. Black HotkeyPrefix=None, LineLimit=False, RightToLeft=False, Trimming=None, WordWrap=True, Angle=0, FirstTabOffset=40, DistanceBetweenTabs=20, Expression Data1 All;Black;1;Solid;False;4;Black Transparent 0,2.8,19,0.4 [216:216:216] True 0.2,0,18.8,0.4 Arial,8 b0b5df8dbafd4026a7a99c6aad0774fb 0,0,0,0 Text4 Say you are running tests in your team builds, and you have configured your build so they can run on a Developer desktop as well as on a build server. By default, using Microsoft’s targets, tests are not run during a Desktop Build. This means that a build can pass when run locally but fail, or give partial success on the server, due to test errors. We had a scenario where some tests were “Not runnable” in our Test Container. Which resulted in failed builds. Black HotkeyPrefix=None, LineLimit=False, RightToLeft=False, Trimming=None, WordWrap=True, Angle=0, FirstTabOffset=40, DistanceBetweenTabs=20, Wysiwyg Expression Data2 All;Black;1;Solid;False;4;Black Transparent 0,4,19,0.4 [157:218:78] True 0.2,0,18.8,0.4 Arial,8 be49b8215c164c949b1c9eb0e4bdebf2 0,0,0,0 Text3 Say you are running tests in your team builds, and you have configured your build so they can run on a Developer desktop as well as on a build server. By default, using Microsoft’s targets, tests are not run during a Desktop Build. This means that a build can pass when run locally but fail, or give partial success on the server, due to test errors. We had a scenario where some tests were “Not runnable” in our Test Container. Which resulted in failed builds. Black HotkeyPrefix=None, LineLimit=False, RightToLeft=False, Trimming=None, WordWrap=True, Angle=0, FirstTabOffset=40, DistanceBetweenTabs=20, Typographic Expression Data3 b39e93679810432b977a37f8632ee4a0 1,1,1,1 Page1 29.7 21 Arial,100 [50:0:0:0] System.Dll System.Drawing.Dll System.Windows.Forms.Dll System.Data.Dll System.Xml.Dll Stimulsoft.Controls.Dll Stimulsoft.Base.Dll Stimulsoft.Report.Dll Report 6/11/2009 3:43:13 PM 6/10/2009 3:21:43 PM C:\Users\Chris\Documents\Stimulsoft_TextWrapping_Report_2.mrt a624d1416519403fa1a4c2092d3b93b8 Report Centimeters 2009.2.413 CSharp