• Support for Internet Explorer 11.

• CurrencyTextBox, PercentTextBox, and the 通貨 and パーセント 選択s in a Validator's DataType 所有物／資産／財産 failed to support Decimal and 選び出す／独身 types.
• CurrencyTextBox and the 通貨 選択 in a Validator's DataType 所有物／資産／財産 failed to use the CultureInfo.NumberFormat.CurrencyGroupSizes 所有物／資産／財産.
• DecimalTextBox did not use the TrailingZeroDecimalPlaces or MaxDecimalPlaces 所有物／資産／財産s.
• When using the String Lookup System, if the value passed in as a LookupID was not 設立する, it would return a blank string instead of the default string. For example, if you have a 支配（する）／統制する with Text="abc" and TextLookupID="code_abc", it should return "abc" when there is no value 蓄える／店d as a 資源 指名するd "code_abc", but instead it returned "".
• Buttons on Calendar, MonthYearPicker, and TimePicker 支配（する）／統制するs whose label 含む／封じ込めるd the 記念品 "{IMAGE}" did not get the image embedded.
• CheckStateValidator did not 正確に attach to <input type='無線で通信する' runat='server' > or <input type='checkbox' runat='server' > tags.
• 除去するd a licensing 制限 on the LinkButton's WhenDisabledCssClass 所有物／資産／財産.
• Date and Time textboxes failed to show the value 割り当てるd to their ToolTip 所有物／資産／財産 when AutoHints were off.
• FieldStateControllers would 注入する the wrong markup when using design 方式 to 追加する 言及／関連s to other 支配（する）／統制するs in its ControlConnection 所有物／資産／財産.
• DateTextBox failed to support the Mongolia (mn-MN) culture during （弁護士の）依頼人-味方する parsing.
• DuplicateEntryValidator would not 適用する its 削減する 所有物／資産／財産 value.
• Peter's Input 安全's 安全 分析 報告（する）／憶測 failed to 生産（高） the many validator 支配（する）／統制するs 設立する on the page.
• MultiSegmentDataEntry 支配（する）／統制するs failed to show 代案／選択肢 style sheets in segments after a postback （悪事，秘密などを）発見するs an error.

• String Lookup System failed to return strings from 資源 とじ込み／提出するs if they were in the BLDErrorMessages, BLDLabels, or DataAnnotations 資源 とじ込み／提出するs.
• When using SQL Server to 蓄える／店 ASP.NET 見解（をとる） 明言する／公表する, this error occurred with a BLDWidgets 支配（する）／統制する: "The 建設者 to deserialize an 反対する of type 'PeterBlum.DES.BLD.BLDWidgetsViewState' was not 設立する."

This 解放（する） is based on the 解放（する） of FireFox v17. That browser changed its 使用者 スパイ／執行官 string in a way that 妨げるs DES from 認めるing the browser. As a result, DES 規模s 負かす／撃墜する features to server 味方する only. There are no javascript elements in FireFox 17.

DES 5.0.4 （悪事，秘密などを）発見するs the new 使用者 スパイ／執行官 which 確実にするs the 十分な （弁護士の）依頼人-味方する experience.

• IntegerTextBox, DecimalTextBox, CurrencyTextBox, and PercentTextBox now 申し込む／申し出 the AllowThousandsSeparator 所有物／資産／財産. By default, 使用者s can type in the thousands separator symbol. When this is 誤った, they cannot and if validation finds this character, it 原因（となる）s validation error.
• IE 10 has poor support for filter styles, a feature introduced by Microsoft in IE 5.5 that 供給するs the 影をつくる／尾行する and fade-in/out 影響s used by DES’s popup elements. The result is a JavaScript error on that browser. IE 10 is now （悪事，秘密などを）発見するd and these features are 無能にするd.
• Compatibility with Telerik RadControls 2012 Q3 解放（する）. Telerik had made changes in their （弁護士の）依頼人-味方する API making some 支配（する）／統制するs have a JavaScript error and others not 実証する 正確に.

• Design 方式 would 報告（する）／憶測 an error instead of 製図／抽選 the 支配（する）／統制する in several 事例／患者s, 予定 to a bug introduced in v5.0.2
• Popup calendar いつかs did not engage keyboard support after a second popup.
• Popup toggle buttons for calendar, monthyearpicker, and timepicker all should have の近くにd the popup when opened. They left it open. These buttons now 行為／法令／行動する as a true toggle.
• （弁護士の）依頼人-味方する 計算／見積り for the length of a string in a textbox counted carraige returns incorrectly on modern browsers. FireFox 15+, IE 9+, and Safari 5+ changed how many characters they 蓄える／店d in memory for each carraige return from two characters (ASCII 13+ ASCII 10) to ASCII 10 alone. On the server 味方する, the browsers always postback ASCII 13+ASCII 10. Now TextLengthValidator and TextCounter 支配（する）／統制する count 2 characters for each carraige return even if they 蓄える／店 only 1 character on the （弁護士の）依頼人-味方する.
• The value of the 示すd checkbox in a CheckBoxList did not work with the CompareToValueValidator or CompareToValueCondition on the （弁護士の）依頼人-味方する.
• When JavaScript is （悪事，秘密などを）発見するd to be 無能にするd, some scripts were still written to the page.
• The mouse over and mouse 負かす／撃墜する 影響s of some buttons with images did not work. This was noticable on the Calendar’s next and previous month/year buttons.
• VisibleCondition, EnabledCondition, and ReadOnlyCondition did not 評価する 正確に on the （弁護士の）依頼人-味方する.
• Calendar part showing the month and year 指名するs did not 適用する the 訂正する style sheet based on the MonthYearCommandAndLabel.CssClass 所有物／資産／財産. It worked 最初 but a mouse over would 適用する an incorrect class.
• CalculationController’s 試みる／企てるd to 割り当てる a decimal value to an IntegerTextBox 原因（となる）ing a TypeCastException when the ShowValueControlID 明示するd an IntegerTextBox.
• Using the Input 安全 module’s LogAndRespond system to 跡をつける an exception or error would 原因（となる） a NullReferenceException if 跡をつけるing an error when using an HttpHandler other than one that 負担s the page.
• The DecimalTextBox, CurrencyTextBox, and PercentTextBox would return the value of Int32.MinValue instead of 二塁打.MinValue when you call their DoubleBindable 所有物／資産／財産 and there is no value 割り当てるd yet.
• The ValidationManager.OnAdjustValidatorToBrowser event would 原因（となる） a NullReferenceException if the browser 原因（となる） the ErrorFormatter to be 取って代わるd. 衝撃d webcrawlers.

• Server-味方する UI-level validation for the RequiredAttribute failed.
• 通貨 FieldTemplates did not use the UseCurrencySymbol 所有物／資産／財産 from the CurrencyDataTypeAttribute.
• パーセント FieldTemplates did not use the UsePercentSymbol 所有物／資産／財産 from the PercentDataTypeAttribute.
• Several exceptions raised by the Filter 支配（する）／統制するs.

Bugs 直す／買収する，八百長をするd

• Web 使用／適用 Updater 報告（する）／憶測d an error when 任命する／導入するing a service 解放（する） that stopped the 過程. The error 示すd a とじ込み／提出する call PeterBlum.DES.BLD3_5.dll which does not ship with the 製品. 明確な／細部 to 5.0.1.
• Validation errors using the HiliteFields and "Change the style of the field with the error" had errors when using ajax or server 味方する only validators 支配（する）／統制するs. They did not 正確に change the 外見 of these fields.
• In FireFox, Calendar 支配（する）／統制する did not fully 無能にする when you 試みる／企てるd to 無能にする it. Usually this 伴う／関わるd using the FieldStateController to 無能にする it, but 使用者s might have tried to 始める，決める the DOME 無能にするd せいにする on the Calendar's div tag. In this 事例／患者, the 支配（する）／統制する appears visually 無能にするd, but still 許すd clicks and keyboard 命令（する）s to 修正する the date.
• Validation with these RadControls Q2 2012 or later 生成するd a javascript error: RadTextBox, RadMaskedTextBox, and RadNumericTextBox.
• BREAKING CHANGE: RadMaskedTextBox validation was inconsistent between （弁護士の）依頼人 and server 味方する validation. Server 味方する validation's methodology is considered 訂正する and 適用するd to the （弁護士の）依頼人-味方する code. Now （弁護士の）依頼人 味方する validation 含むs the text 挿入するd by the mask, just like using the RadMastedTextBox.ValidatedText 所有物／資産／財産 does. 以前, validation only looked at the text the 使用者 enters, ignoring the text 挿入するd by the mask.
• IE 9 changed how to turn off autocomplete. This is now 直す／買収する，八百長をするd.
• When 実証するing with the PopupErrorFormatter and PageManager.FocusOnSubmit=true, if the validator with the PopupErrorFormatter 報告（する）／憶測s a server 味方する error, 焦点（を合わせる） did not jump to that validator's 支配（する）／統制する to 評価する. It now does.
• IgnoreConditionValidator now automatically 設立するs （弁護士の）依頼人-味方する javascript for its ErrorFormatter. 以前 you had to 始める，決める the OverrideClientSideEvaluation 所有物／資産／財産.

• Supports the recently 解放（する）d Telerik RadControls 2012 Q1 解放（する）. This 解放（する） changed the IDs to the HTML elements of the 支配（する）／統制するs, breaking 存在するing scripts. 取り付け・設備 of 5.0.1 is enough to get it to work. There are no 付加 とじ込み／提出するs to 任命する／導入する.
• Cleaned up how memory is 性質の／したい気がして so that when a 支配（する）／統制する is 除去するd from the tree, its memory is usually 解放（する）d 権利 away instead of waiting for the .逮捕する Garbage Collector to 配置する／処分する／したい気持ちにさせる it.
• New 所有物／資産／財産: HeaderSeparator in the ValidationSummary 支配（する）／統制する. It 無視／無効s the default text 挿入するd after the Header to separate it from the 名簿（に載せる）／表（にあげる）.

• CurrencyTextBox: The AllowExtraDecimalDigits 所有物／資産／財産 行為／法令／行動するd as if it was 始める，決める to true when the 所有物／資産／財産 was left to its default. It should 行為／法令／行動する as if it was 始める，決める to true (not 許すing extra decimal digits.)
• CurrencyTextBox, DecimalTextBox, and PercentTextBox: The AcceptPeriodAsDecimalSeparator 所有物／資産／財産 threw a TypeCastException.
• IntegerTextBox: The FillLeadZeros 所有物／資産／財産 did not work after a postback. The server 味方する code that reformats failed to account for it. （弁護士の）依頼人-味方する code worked 正確に.
• Validators using DataType="パーセント" but not pointing to a PercentTextBox should have 要求するd only integers. They 許すd decimals too.
• DateTextBox: The position of the popup calendar was overlapping the textbox and toggle image. Now it positions at the 底（に届く） of the image. (If the image is smaller than the textbox, it will still overlap.)
• Validators: When 含む／封じ込めるd in a 支配（する）／統制する that is 明白な=誤った, server 味方する validation still occurred. It should have not 実証するd.
• Design 方式: several 所有物／資産／財産s that have not been 修正するd were getting written out into the ASP.NET markup when you edit another 所有物／資産／財産 in the 所有物／資産／財産s Editor. This occurred in a few 支配（する）／統制するs.
• SpecialDates in Design 方式: The editor for TokenDefinitions and DataFieldsWithTokens failed when you clicked the 追加する button.
• MultiConditionValidator and MultiCondition 反対する in Design 方式: the Editor for the 条件s 所有物／資産／財産 failed when you 試みる／企てるd to 追加する a child 条件.
• FieldStateControllers in Design 方式: the Editor for the Enabler 所有物／資産／財産 would not 令状 out changes.
• FieldSecurityValidator in design 方式: Did not draw 正確に.
• ValidationSummary: Using the AddMessage() method would show your text after the （弁護士の）依頼人-味方する 除去するs other messages from validators which the 使用者 訂正するd.

• PageSecurityValidator now 始める，決めるs the DetectInjection 所有物／資産／財産 to true on ParameterRule, HiddenFieldRule, and CookieRule 反対するs.
  DetectInjection is 適用するd when these 反対するs have their DataType 所有物／資産／財産 始める，決める to Ignore or String. The documentation 以前 said DetectInjection defaults to true, but the code defaulted to 誤った. This not only 訂正するs the documentation with the code, but chooses the more 保護の approach of enabling 安全.
  This is a breaking change for 使用者s who have defined these 反対するs with DataType=Ignore or String, and do not want DetectInjection to be true. If your 支配する 反対する explicitly 始める，決めるs DetectInjection to 誤った, you're code will not break. You should review your PageValidationSecurity 支配（する）／統制するs for 反対するs defined in their ParameterRules, HiddenFieldRules, and CookieRules 反対するs. 事例／患者s to look for:
  • The DataType 所有物／資産／財産 is not 割り当てるd. It uses Ignore as its default.
  • The DataType 所有物／資産／財産 is 割り当てるd to Ignore or String.
  • The DetectInjection 所有物／資産／財産 is not 割り当てるd. 決定する if you want to 保護する against SQL 注射 and Cross 場所／位置 Script 注射 attacks (recommended). If you do not, 始める，決める this 所有物／資産／財産 to 誤った.
• The PageSecurityValidator's new DetectDatabaseElementNamesInQueryString 所有物／資産／財産 衝撃s query string parameters ーするつもりであるd to 受託する strings, when a string it 許すs is also defined in the <databaselementnames> node of the master.config とじ込み／提出する.
  Look for any query string parameter that 受託するs a string type. If it should 受託する one of your database element 指名するs, 始める，決める this 所有物／資産／財産 to 誤った and use the ParameterRule 反対する with its DetectInjection 所有物／資産／財産 始める，決める to true. DetectInjection 適用するs a more コンビナート／複合体 algorithm to 決定する if a database element 指名する is 合法的な or not.

• New 所有物／資産／財産 on PageSecurityValidator: DetectDatabaseElementNamesInQueryString. When true, look at the entire query string for any value defined in the <databaseelementnames> node of the master.config とじ込み／提出する and 報告（する）／憶測 an error if 設立する. It defaults to true and may be a breaking change. See above.
  This 所有物／資産／財産 is in 返答 to the lizamoon attack (starting in March 2011) which creates an update 声明 using （米）棚上げする／（英）提議する and field 指名するs it already 抽出するd from a 事前の attack on your database's master （米）棚上げする／（英）提議するs:
  update [your （米）棚上げする／（英）提議する 指名する] 始める，決める [your field 指名する] = REPLACE(and so 前へ／外へ)
• The TextBox.DisablePaste 所有物／資産／財産 now 作品 with FireFox.
• The EnterSubmitsControlID 所有物／資産／財産 on TextBoxes and NativeControlExtender now support LinkButtons on FireFox.
• DES Buttons 申し込む／申し出 MayMoveOnClick 所有物／資産／財産 but it was not supported when CausesValidation=誤った. It is now supported in that 事例／患者.
• The 警報 shown by the PageManager.ShowAlertOnSubmit and PeterBlum.DES.全世界のs.Page.ShowAlertOnSubmit 所有物／資産／財産s now supports the {COUNT} and {COUNT:singular:plural} 記念品s. They show the number of errors 名簿（に載せる）／表（にあげる）d.

• Internet Explorer 9 報告（する）／憶測d a javascript error when 負担ing pages that used scripts associated with date and time data.
• When using AJAX to preload features, the preload 選択 "TimeTextBoxes" needed to 負担 付加 scripts when there was no DateTextBox also on the page.
• When using AJAX with a CalculationController with an 大（公）使館員d validator, the validator would not see the CalculationController after a callback.
• When using the ConditionCalcItem on a CalculationController, and the 条件 was not one of the most ありふれた ones, a javascript error occurred.
• When using the NumericTextBoxCalcItem on a CalculationController, and the textbox used was a PercentTextBox, the value from the textbox was not 含むd in the 計算／見積り.
• The PageManager.HintManager.PopupOnFocusDelay 所有物／資産／財産 was ignored.
• When using the CombinedErrorMessages 支配（する）／統制する with its NoErrorFormatter 体制／機構, the NoErrorFormatter would not always appear based on the 体制／機構.
• When using the System.Web.UI.WebControls.RequiredFieldValidator with a DateTextBox, some 事例／患者s had javascript errors.
• When using native button 支配（する）／統制するs with Medium 信用 安全 on your app, a 安全 exception may have occurred.
• The ValidationSummary would draw a <br /> tag if there was HeaderText to show but no 団体／死体 (DisplayMode=非，不，無) and no footer. It left an extra line.
• The PeterBlum.DES.全世界のs.Page.SubmitHidesOtherValidationGroups 所有物／資産／財産 was not considered during an AJAX callback. When its 誤った, it should redraw other validation groups. It did not.
• When the page gets style sheets by 挿入するing <% PeterBlum.DES.StyleSheetManager.GetLinkTags() %>, it did not 適用する XHTML formatting to the resulting Link tag.
• Spinners on さまざまな textboxes 前進するd by 2 instead of by 1 when clicking very quickly on most browsers.
• Chrome and later Safari browsers positioned the popup calendar's toggle button much lower than it should be. This is because the style="提携させる:最高の，を越す;" was used for all browsers and these two browsers worked 異なって. Now 提携させる:text-最高の，を越す is used for these browsers. This change also 影響s the popup toggle for the MonthYearPicker with the Calendar 支配（する）／統制する.

• Support of ASP.NET 4 問題／発行する where ClientIDMode=Predictable is 体制／機構 on these 支配（する）／統制するs, any コンテナ 支配（する）／統制する, the page, or globally.
• The Calendar's 拡大するd Day 見解（をとる） can now be popped up by a click as an 代案／選択肢 to a mouse over. 始める，決める Calendar.ExpandedFormatter.PopupOnClick to true.
• When your host uses a Medium 信用 方式, you can get a SecurityPermission exception referring to ConfigurationPermission. 追加する this 入ること／参加（者） to the <appSettings> section of your web.config とじ込み／提出する:
   <追加する 重要な="DES_DisableHttpHandlerCheck" value="" />
  

• Reworked how to pass 所有物／資産／財産s to FieldTemplates from DES.UIHintAttribute, DES.DynamicField, DES.DynamicControl, and DataFieldInPattern. It uses the same 所有物／資産／財産s more efficiently and programmatic support is better. In 新規加入, DES.DynamicField did not 正確に support this feature until now.
• New FieldTemplate for AJAX 支配（する）／統制する Toolkit (May 2009) 使用者s: Html_Edit.ascx. It uses the new HTMLEditor 支配（する）／統制する.
• Support for CategoryAttribute in your field-level 商売／仕事 logic. Use 部類s to define scaffolding groups and to select NamedStyles in PatternTemplates. With NamedStyles, you can differentiate 確かな fields such as the "指名する" field from others with a different style sheet by creating a 部類.
• ScaffoldColumnAttribute can 明示する scaffolding by 方式: ReadOnly, Edit, and 挿入する.
• 安全 役割s supported. 含むs the TableRestrictionAttribute and ColumnRestrictionAttribute for your metadata and NamedStyles can 明示する a 役割.
• CombinedErrorMessage 支配（する）／統制する using a PopupErrorFormatter will now refresh as errors change when the PopupView is already open.
• When using the FSCOnCommand and MultiFSCOnCommand 支配（する）／統制するs, the 初期の 外見 of 支配（する）／統制するs to change was 不明瞭な. Did the 支配（する）／統制する 設立する them or not? Now it 設立するs them by default and 申し込む／申し出s the SetInitialAppearance 所有物／資産／財産 to change this 行為.

• Internet Explorer 8 扱うd setting the "innerHTML" 異なって, 妨げるing event handlers from 存在 挿入するd once the page 負担 is 完全にする. This broke the ClientSideCreatesHTML 所有物／資産／財産 始める，決める to "FirstPopup" on any 支配（する）／統制する that can popup. It also broke the の近くに box on the 拡大するd Date 見解（をとる） popup for the Calendar 支配（する）／統制する.
• Popup calendar had sizing 問題／発行するs when using the MultiMonthColumnCount 所有物／資産／財産. The field with the month 指名する was 2 pixels too wide. FireFox and オペラ needed better sizing of the 全体にわたる width to 避ける months overlapping the 権利 辛勝する／優位 of the 支配（する）／統制する.
• When a TextBox using ValueWhenBlankCssClass is updated in an AJAX callback and it has an associated validator that changes the style of the textbox to show an error, the ValueWhenBlankCssClass was not shown after the callback until the 使用者 visited the field.
• When the page is scrolled, Safari and オペラ いつかs incorrectly positioned any popup if the popup is 含む／封じ込めるd in a style="position:直す／買収する，八百長をするd" element
• FireFox 3 would 許す popups to 延長する beyond the 明白な area of the page. It should have 転換d into the page, like the other browsers do.
• The CreditCardNumberValidator was 文書d to have the CleanedUpNumber 所有物／資産／財産. It is now 利用できる.
• Input 安全 Script 注射 did not （悪事，秘密などを）発見する the <h1> - <h6> as HTML tags to 実証する.
• In cultures that use ASCII 160 for the group separator character, validation of any numeric textbox may consider the letter "A" as 合法的な in the number. 設立する with the Czech (cs-CZ) culture.
• The CalculationController.LabelToken 所有物／資産／財産 did not work 訂正する after a postback or when the 記念品 was "{0}".
• When a DES TextBox has AutoPostBack=true and AutoPostBackValidates=誤った, it still 試みる／企てるd to 成し遂げる （弁護士の）依頼人-味方する validation on the textbox 事前の to a postback.
• The MultiSelectionCalendar 許すd 選択s 事前の to the MinDate and after the MaxDate 所有物／資産／財産 values.
• The CalculationController いつかs had a slight 一連の会議、交渉／完成するing error when using the 一連の会議、交渉／完成するing 方式 of 通貨.
• When the DateTextBox uses the RangeEndSetsMinDate 所有物／資産／財産, it was incorrectly setting it one date too 早期に.
• On a MultiSegmentDataEntry 支配（する）／統制する where segments are textboxes and TabOnMaxLength is true, いつかs moving to a segment that has the 最大限 text autotabbed over that segment.

• Documentation reformatted. 取り付け・設備 directions 改善するd.
• 議会 supports 部分的な／不平等な 信用 環境s
• The question can now be positioned to the left of the answers by using the xQuestionToLeftOnEntryB and xQuestionToLeftOnResultsB 所有物／資産／財産s.
• The xRotatingPollsEntryOnlyB 所有物／資産／財産 is an 拡大 of the xRotatingPollsB 所有物／資産／財産. When true, each 投票（する） is followed 入ること／参加（者） 方式 showing the next question. It's 基本的に a way to go through a 一連の questions one-by-one like a 調査する.
• New event: PollCreating. Use it to update the 投票 支配（する）／統制する’s 所有物／資産／財産s or take another 活動／戦闘 すぐに 事前の to when a 投票 記録，記録的な／記録する is 変えるd into the content on the page. This event 供給（する）s you with the 現在の 見解（をとる）, 投票 記録，記録的な／記録する, and 投票 count amongst 多重の 投票s shown, all in the Args parameter.
• RecentPolls now identifies the 記録，記録的な／記録する ID of the 現在／一般に shown 投票 within its xPollID 所有物／資産／財産

• The 投票's PreRender event was not supported.
• ASP.NET 2 遺産／遺物 方式 could いつかs 妨げる saving the value of a 投票（する）. The 投票 would re-appear in 入ること／参加（者） 方式 after submission.

• For Input 安全 使用者s. When the FieldSecurityValidator or PageSecurityValidator have their HtmlTagMode 所有物／資産／財産 始める，決める to IllegalExceptTags and their HTMLTags 所有物／資産／財産 始める，決める to "", the 行為 has changed. 以前 it 扱う／治療するd all tags not 宣言するd in the <illegaltags> section of the config とじ込み／提出する as 合法的な. Now it 扱う／治療するs them all as 違法な, which makes more sense. The HTMLTagMode and HTMLTags 所有物／資産／財産s default to IllegalExceptTags and "" それぞれ, so if you are using their default values and you want to 許す all tags not in the config とじ込み／提出する to be 受託するd, you must change HTMLTagMode to AllLegal.
• For DES Dynamic Data 使用者s. There is a major 精密検査する of PageTemplates and the DynamicDataManager 支配（する）／統制する. The 場所s of the PageTemplates and FieldTemplates folders have changed 同様に. If you have customized the PageTemplate とじ込み／提出するs, be 用意が出来ている to migrate your changes into the new PageTemplate とじ込み／提出するs.
• The native ImageButton 支配（する）／統制する and as a result, DES's ImageButton 支配（する）／統制する, failed to 解雇する／砲火／射撃 their Click or 命令（する） event handlers when using FireFox (any 見解／翻訳／版) if the browser could not 負担 the image. They may have left ImageUrl unassigned, it had an 無効の URL, or the server failed to retrieve the image. DES's ImageButton now 解雇する／砲火／射撃s the Click and 命令（する） event handlers in this 事例／患者.

• 認めるs the Google Chrome browser and 作品 正確に both in scripts and 外見. The TrueBrowser class now identifies three separate values for さまざまな 関係のある browsers: AppleWebKit (the underlying 科学（工学）技術 for both Safari and Chrome), Safari, and Chrome.
• LocalizableLabel has 高めるd the AssociatedControlID 所有物／資産／財産. It now 作品 with an ID 存在 in any ancestor 指名するing コンテナ. 加える the new AssociatedControl 所有物／資産／財産 where you can 割り当てる a 言及／関連 to the other 支配（する）／統制する 設立する in any 指名するing コンテナ.
• When using 多重の validation groups, clicking on a 服従させる／提出する button would not hide the validation errors associated with other validation groups. This could be distracting to the 使用者 since they will try to 直す／買収する，八百長をする errors 関係のない to the validation group. Now it （疑いを）晴らすs those errors. If you like the previous way, 始める，決める PeterBlum.DES.全世界のs.Page.SubmitHidesOtherValidationGroups to 誤った in Page_Load.
• When using the ExtraControlsRunThisAction 所有物／資産／財産 on a validator 連合させるd with the ChangeStyleOnControlsWithError 所有物／資産／財産, 支配（する）／統制するs in the ExtraControlsRunThisAction 所有物／資産／財産 would get their style sheet class changed. This 行為 doesn't seem 権利 and has been turned off by default. If you like the previous way, 始める，決める PeterBlum.DES.全世界のs.Page.ChangeStyleOnControlsWithErrorIncludesExtraControls to true in Page_Load.
• Two new javascript 機能（する）／行事s 利用できる to change the 外見 of a validator: DES_UpdVal() and DES_HideVal().
• When using the ShowAlertOnChange 所有物／資産／財産 (on PageManager or the 全世界のs.Page 反対する), it used to show the ErrorMessage 所有物／資産／財産 on the validator. The SummaryErrorMessage is usually more 完全にする. So now it shows the SummaryErrorMessage by default (落ちるing 支援する to the ErrorMessage 所有物／資産／財産 when SummaryErrorMessage is blank). You can return to using only the ErrorMessage 所有物／資産／財産 by setting AlertShowsSummaryMessage to 誤った in the PageManager or 全世界のs.Page. It can be 始める，決める globally with the DefaultAlertShowsSummaryMessage 所有物／資産／財産 in the 全世界の Settings Editor.
• New 所有物／資産／財産 on Calendar and MultipleCalendar: SelectedOtherMonthCssClass. Lets you 割り当てる a different style sheet class to day 独房s in the "other month" when using 多重の Month 見解（をとる）. Without it, those day 独房s do not show any 選択.
• GZIP and DEFLATE compression 加える better （弁護士の）依頼人-味方する （武器などの）隠匿場所ing is now supported by the とじ込み／提出する-based retrieval of scripts and style sheets. (You have 体制／機構 the <追加する 重要な="DES_GetFilesVirtualPath" /> in the web.config とじ込み／提出する. If you are using the HttpHandler which is the default, these features already 存在する.)
• Your own style sheets can now be compressed and 合併するd with DES's style sheets. See the topic "Support for your own style sheets" in the "Using Style Sheets" section of the "General Features Guide".
• Any style sheet とじ込み／提出する that uses DES's compression and 合併する supports URL 記念品s "~/" and "{APPEARANCE}" within the url() 記念品 of the background and background-image styles.
• Google Chrome browser fails to 扱う DropDownList.AutoPostBack=true when that DropDownList is 大（公）使館員d to either a native or DES validator. Now you can attach a NativeControlExtender to the DropDownList and it will 体制／機構 AutoPostBack in a way that 作品 with Chrome, 関わりなく whether you want to 実証する 事前の to postback.
• The ValueWhenBlank feature on textboxes now supports the Reset button. It 設立するs the 訂正する text and style sheet depending on how Reset changed the textbox.
• The TextCounter 支配（する）／統制する now changes the style of the textbox when the length 越えるs or 減少（する）s below the 最大限. It 要求するs the Validator's ChangeStyleOnControlsWithErrors 所有物／資産／財産 is 始める，決める to true. (Its 始める，決める on the PageManager or PeterBlum.DES.全世界のs.Page 反対する.) It will also hide the TextLengthValidator if its showing as the length is 減ずるd.
• 改善するd （犯罪，病気などの）発見 of javascript by running the 実験（する） code very 早期に. That 妨げるs most javascript errors occurring on the 初期の page 負担d from skipping the 実験（する） code, and その為に making the postback think no scripts are running.
• Within the Validator's NoErrorFormatter, its Text 所有物／資産／財産 now can use the "{IMAGE}" 記念品 to place the ImageUrl's image tag inside the Text.
• AJAXManager now supports preloading the Spinner feature used by numeric and time textboxes.
• TimeOfDayTextBox and DurationTextBox have a new 所有物／資産／財産: CommandsFireOnChangeFunction. When OnChangeFunctionName is 割り当てるd, this 決定するs if edit 命令（する）s 解雇する／砲火／射撃 your onchange 機能（する）／行事. It 許すs for more interactive 行為 when OnChangeFunctionName is used.
• IE would （武器などの）隠匿場所 scripts and style sheets 分かれて for each folder identified in a URL. It now （武器などの）隠匿場所s them once per 場所／位置. (Associated with the DESGetFiles HttpHandler.)
• There were 事例／患者s where garbage collection could occur earlier and 減ずる the memory 需要・要求する on the server that are now 演説（する）／住所d.

• PatternTemplates introduced. PatternTemplates are perhaps the most important 道具 to creating web forms. They are 使用者 支配（する）／統制するs that 含む／封じ込める a 封鎖する of HTML and さまざまな 支配（する）／統制するs ? 含むing DynamicControls ? that 述べる a pattern. Your ListView and FormView 支配（する）／統制するs 要求する much いっそう少なく 体制／機構 because instead of 令状ing the HTML and 支配（する）／統制するs of a pattern, you 含む a PatternTemplate by 明示するing its 指名する in a DynamicPattern 支配（する）／統制する.
• DynamicListView and DynamicFormView 支配（する）／統制するs introduced. They subclass ListView and FormView to 供給する the 緩和する of 体制／機構 設立する in GridView and DetailsView. They let you fully 支配（する）／統制する the HTML 生産（高） by using PatternTemplates. As a result, the PageTemplate とじ込み／提出するs are now using them instead of GridView and DetailsView. Now your PageTemplates can have their HTML customized through the PatternTemplates instead of creating a new PageTemplate とじ込み／提出する.
• DynamicColumnTitle 支配（する）／統制する introduced. Used in a columnar style interface to give column 肩書を与えるs a sorting 使用者 interface.
• DynamicControlPanel 支配（する）／統制する introduced. This 支配（する）／統制する 拡大するs upon the DataPager 支配（する）／統制する from ASP.NET 3.5 to 申し込む／申し出 far more 道具s that manipulate the contents of your databound page. There are many types of pagers, sorting 選択s, page size 選択s, and editing buttons.
• DynamicButtons 支配（する）／統制する introduced. 生成するs the 基準 buttons used on databound 支配（する）／統制するs like New, Edit, Save, and 取り消す. Very 柔軟な. You can 始める，決める it up using 所有物／資産／財産s or Templates.
• DES.ScaffoldColumnAttribute introduced. It subclasses the native ScaffoldColumnAttribute, 追加するing 所有物／資産／財産s that 許す ordering of the column, by column number, 親族, and after a 明示するd column 指名する.

• When a CheckBox or RadioButton 支配（する）／統制する is 無能にするd by the FieldStateController, if its parent HTML tag is a <td> without an id= せいにする, everything 含む／封じ込めるd in that （米）棚上げする／（英）提議する 独房 would be 無能にするd. (A workaround is to 割り当てる an id= to the （米）棚上げする／（英）提議する 独房 tag.)
• The Calendar 支配（する）／統制する いつかs had its week 列／漕ぐ／騒動s overlap the 権利 国境 in FireFox 3 and IE 7.
• The MultiSelectionCalendar did not use the mouse over 影響 on day 独房s that also had the 範囲 hiliting 影響.
• These two （弁護士の）依頼人-味方する 機能（する）／行事s for DateTextBox did not work: DES_DTBSetMinDate() and DES_DTBSetMaxDate().
• When a TimePicker has the time "0:00" (12 midnight), that value would be 扱う／治療するd as "no 選択" instead of the actual time. 影響する／感情d PopupTimePicker, TimeOfDayTextBox with TimePicker and DurationTextBox with TimePicker.
• When a popup was on 最高の，を越す of an element whose style is position:直す／買収する，八百長をするd and the main window was scrolled, the popup was incorrectly positioned.
• The MultiCondition and MultiConditionValidator had differences in how their （弁護士の）依頼人-味方する and server 味方する evaluation 機能（する）／行事s worked when a child 条件 returned "cannot 評価する". The server 味方する code has been changed to match the （弁護士の）依頼人-味方する code.
• The DecimalMode 所有物／資産／財産 on TimeOfDayTextBox and DurationTextBox did not 許す 入ること／参加（者） of a decimal character when it was 始める，決める to "TimeSeparator".
• Design 方式 did not 名簿（に載せる）／表（にあげる） MultipleRequiredControlsCondition in editors for the Enabler or MultiCondition.
• The MultipleRequiredControlsValidator いつかs threw a NullReferenceException when 居住させるing its RequiredControlsToEvaluate 所有物／資産／財産 in the ASP.NET Declarative Syntax.
• A SpecialDates style sheet on a Calendar's Day 独房 did not 許す the style sheet for Today's Date to be 適用するd. Today's date style sheet should have been 合併するd.
• When using the SlowDownManager of the Input 安全 module, an InvalidCastException いつかs appeared from the CheckForwarded_For_IP() method.
• Validation ErrorMessage and SummaryErrorMessage 所有物／資産／財産s that 含む／封じ込める a 選び出す／独身 \ character would 陳列する，発揮する two \ characters.
• The MultipleRequiredControlsValidator 報告（する）／憶測d the page is 無効の on the server 味方する when all 支配（する）／統制するs it 評価するs are 明白な=誤った (such as hidden in a page of a Wizard that is not 明白な).
• The DataTypeCheckValidator should support the ReportErrorsAfter 所有物／資産／財産 when the DataType="DateTime".
• The LastSelectedDate 所有物／資産／財産 on MultiSelectionCalendar 生成するd a stack 洪水 exception.
• When MultiSelectionCalendar is in 範囲 方式, the hiliting and associated date 範囲 appearing in the Message 中心 would 含む or 除外する one too many dates. Any click to 適用する that 選択 would still have the 訂正する results.
• When javascript is 無能にするd and an 不法に formatted number is entered into Integer, Decimal, 通貨, or PercentTextBox, the DataTypeCheckValidator does not 報告（する）／憶測 an error, yet an 試みる／企てる to get the number through any "Value" 所有物／資産／財産 on these textboxes threw a FormatException.
• DES's HtmlButton and HtmlInputButton 支配（する）／統制するs threw a TypeCast exception on postback from their OnServerClick event handler.
• The "Now" 命令（する） on the TimeOfDayTextBox 始める，決める the 大（公）使館員d DateTextBox one day ahead depending on the 現在の time and timezone.
• When the date 判型 of YYYY-MM-DD is used on a RangeValidator's 最小限 and 最大限, or on the CompareToValueValidator, or in the DateTextBox, 確かな time zones 変えるd the string entered to the previous day.
• When PeterBlum.DES.全世界のs.Page.MoreCultureInfo.AdditionalDateSeparators has two or more characters, （弁護士の）依頼人-味方する code failed to 受託する any of those characters in the DateTextBox. It would 報告（する）／憶測 validation errors instead of 変えるing the separators to their default value. It worked 正確に on postback.
• Infragistics WARP 科学（工学）技術 now better supported by the AJAXManager. Scripts are more reliably 負担d 避けるing javascript errors.

• Validation support for Infragistics WebTextBox 支配（する）／統制する
• New 所有物／資産／財産 on MonthYearPicker: ReverseYearOrder. Used in 判型=FewYears. It shows the 最新の year first and the earliest year last.
• Support for 生産／産物 servers that 課す the FIPS 安全 支配する where you see this exception: "Rijndael 実施 is not part of the Windows 壇・綱領・公約 FIPS 実証するd cryptographic algorithms". You will also need a new license とじ込み／提出する that is encoded 異なって. To get it, go to http://www.peterblum.com/getorder.aspx. Enter your email 演説（する）／住所 and serial number. It will expose a checkbox "I am using either Peter's Data 入ること／参加（者） 控訴 or one of its modules, and I have v4.0.4 or higher." 示す that to have FIPS compliant license とじ込み／提出するs 配達するd. 取って代わる 現在の とじ込み／提出するs with the new ones.

• New FieldGenerator class to let you 支配（する）／統制する how (a)自動的な／(n)自動拳銃 scaffolding 作品 through the new IFieldGeneratorGuidance interface 適用するd to your master page. There are 広範囲にわたる ways to customize the DynamicField 名簿（に載せる）／表（にあげる） 生成するd by (a)自動的な／(n)自動拳銃 scaffolding, often 除去するing the need to create a duplicate PageTempate in the CustomTemplates folder.
• New FieldTemplates: DbImage (for binary columns 含む／封じ込めるing images), Url (for strings that are Urls), UrlAsImage (for Urls pointing to images), DateAjaxCalendar_Edit (uses the Ajax 支配（する）／統制する Toolkit's CalendarExtendr), IntegerSlider_Edit (uses the Ajax 支配（する）／統制する Toolkit's SliderExtender), and three ways to 陳列する，発揮する booleans (with checkbox, image, and label).

• When the ToolTip for a DES button has a linefeed (\r\n) or 多重の 選び出す／独身 引用するs, a javascript error occurred.
• Infragistics WebEditor 支配（する）／統制するs that are 追加するd after an AJAX update did not get their "onchange" validation 影響s. They did 正確に 実証する on the （弁護士の）依頼人-味方する when the 使用者 試みる／企てるd to 服従させる／提出する.
• When using AJAX on a Validator whose DataType=通貨 and it 評価するs a native TextBox, if you don't have a license covering Peter's TextBoxes, it gave a javascript error.
• XHTML validation error on the querystring parameters of the <script src='DESGetFiles.aspx' /> tag has been 直す／買収する，八百長をするd.
• When using the CalculationController with its RoundMode 所有物／資産／財産 始める，決める to Round5, some 計算／見積りs 原因（となる）d values that get incorrectly 一連の会議、交渉／完成するd 負かす／撃墜する when they should have 一連の会議、交渉／完成するd up.
• When using AJAX with "模造の" Calendar or MultiSelectionCalendar and you are using its ExpandedDateFormatter feature, a javascript error occurred as the page opened.
• A javascript error occurred when using a calendar with the ExpandedDateFormatter in the に引き続いて 状況／情勢: the ExpandedDateFormatter is 明白な (popped up) and the 使用者 試みる／企てるs to open anything else that pops up, such as the MonthYearPicker or ContextMenu.
• When using a numeric TextBox with its ValueWhenBlank 所有物／資産／財産 始める，決める, if validation has the に引き続いて settings, the 使用者 may be 絶えず 直面するd by 警報s: PageManager.ShowAlertOnChange=true PageManager.FocusOnChange=true RequiredTextValidator on the textbox.
• In FireFox, a textarea tag 扱う／治療するs carriage returns 異なって than other browsers. The length of a carriage return is 1 character in FF and 2 in others. This 影響する／感情s TextCounter and TextLengthValidator (on the （弁護士の）依頼人-味方する) as they 評価する 異なって for the browsers. The code has been adjusted to make FF count each carriage return as 2.

• Prerelease of "DES Dynamic Data" is 利用できる in the Dynamic Data folder. This will become v4.1 when its finished (it will be a 解放する／自由な update for v4 使用者s).
  It 配達するs support for ASP.NET Dynamic Data and 非常に／多数の enhancements to that system. Please give it a try and 供給する feedback so this ソフトウェア is 正確に 器具／実施するd.
• Scripts and style sheets are now 配達するd using GZIP or DEFLATE compression on browsers that support it. This 要求するs the DESGetFiles.aspx HttpHandler to be active.Most browsers support this. However, 予定 to bugs in IE6's 実施, this feature is 無能にするd on that browser.
• New 所有物／資産／財産: AutoHintStyle. On all Date and Time textbox 支配（する）／統制するs. 拡大するs your 支配（する）／統制する over the AutoHint feature, letting you 選ぶ from さまざまな styles, such as tooltip or hint.
• New 所有物／資産／財産: AutoHintAppendsToHint. On all Date and Time textbox 支配（する）／統制するs. 拡大するs the AutoHint feature to 許す the text 割り当てるd to the Hint 所有物／資産／財産 to be 合併するd with the AutoHint text.
• Calendar and MultiSelectionCalendar now can identify what invoked your OnSelectionChangedScript by 実験（する）ing the 地元の variable vApply. If true, the 適用する button was clicked. 誤った when the 選択 was changed.
• Scripts are now using the preferred 基準 of //<![CDATA[ as …に反対するd to <!--.

• The HintFormatter.HiddenOnError 所有物／資産／財産 should also take into account if the validator's NoErrorFormatter is 陳列する，発揮するd. It should not show the hint in that 事例／患者 as the goal of HiddenOnError is to 避ける having both the validator's info and the hint on the 審査する at the same time.
• When Validator.NoErrorFormatter.方式 is 始める，決める to "訂正する", it did not 陳列する，発揮する the NoErrorFormatter if the first 活動／戦闘 the 使用者 took was to enter 訂正する （警察などへの）密告，告訴（状）. It appearred only if they edited the field a second time.
• When a validator uses OverrideClientSideEvaluation=Callback and ReportErrorsAfter uses any form of "AllEdits", a javascript error occurred after the callback.
• The 資源s とじ込み／提出するs 供給（する）d for the String Lookup System were 欠如（する）ing "DESMisc.resx"
• When using AJAX to preload a ValidationSummary with the PageManager.PreloadForAJAX-ValidationSummary 所有物／資産／財産, or calling AJAXManager.PreRegisterForAJAX(ValidationSummary), a Javascript error still occured after the callback.
• When using AJAX to preload a TextBox and the textbox uses the ValueWhenBlank 所有物／資産／財産s, a javascript error referring to "DES_VWBInit" occured on the callback.
• When using PageManager or DESPage.ChangeStyleOnControlsWithError and you make a validator 無効の on the server 味方する, the 支配（する）／統制する with the error could get stuck showing the error style sheet even after it was 直す／買収する，八百長をするd.
• When using PageManager or DESPage.ChangeStyleOnControlsWithError, a RadioButtonList or CheckBoxList with RepeatLayout=（米）棚上げする／（英）提議する will incorrectly show the error style sheet after the error gets 訂正するd (no postback or callback 伴う／関わるd).
• When in an AJAX Callback, if a DateTextBox 始める，決めるs a 所有物／資産／財産 on either its PopupCalendar or Calendar child 所有物／資産／財産s, a Typecast exception was thrown.
• When in an AJAX Callback, if a 支配（する）／統制する created during the callback needs different CultureInfo features on the （弁護士の）依頼人-味方する, they were not 供給（する）d. The 支配（する）／統制する would not 申し込む／申し出 the 訂正する culture info settings. In some 事例／患者s, the 支配（する）／統制する will 生成する a Javascript error.
• The FieldStateController ignored changing its Enabled 所有物／資産／財産 during a postback if server 味方する validation already occurred.
• Script and style sheet とじ込み／提出するs 配達するd by the DESGetFiles.aspx HttpHandler were not （武器などの）隠匿場所ing on the browser.
• Third party 支配（する）／統制するs that 宣言する an <InitScript> tag in the <ThirdPartyControls> section of the custom.des.config とじ込み／提出する would fail to run that 機能（する）／行事 if they are first 負担d after an AJAX callback.
• When using an AJAX Callback, server 味方する validators that 報告（する）／憶測 an error did not 反映する that error on the ValidationSummary or the 警報 shown when using PageManager.ShowAlertOnSubmit.
• There was a licensing error 需要・要求するing Peter's Profession Validation when you don't have that license and use any DES TextBox's AutoPostBack 所有物／資産／財産.
• When a hint's text 含むd a carriage return character, a javascript error could occur.
• PageManager 支配（する）／統制する was 行方不明の a 所有物／資産／財産 to 始める，決める the PreLoadForAJAX-CombinedErrorMessages 所有物／資産／財産.
• When using a CustomValidator without its ControlToEvaluate 所有物／資産／財産 割り当てるd, a javascript error could occur during an AJAX callback.
• When using a パネル盤 with any DES TextBox 支配（する）／統制するs and that パネル盤 is 明白な=誤った 最初, if you 始める，決める it to 明白な=true during an AJAX callback, the DES textbox 支配（する）／統制するs will not 陳列する，発揮する although they should.
• When using design 方式 in Visual Studio 2008, the 取り消す button on the 所有物／資産／財産 editor for a 条件s 所有物／資産／財産 will 衝突，墜落 VS2008.

• BREAKING CHANGE: The TextCounter now 申し込む／申し出s the NoLimitMessage 所有物／資産／財産. It is used instead of the NormalMessage 所有物／資産／財産 when there is no 最大限 明示するd. The default text of the NormalMessage 所有物／資産／財産 has been changed to "{COUNT} of {MAXIMUM} characters". If you are using the default text on NormalMessage and you want the 初めの text, 割り当てる it to "{COUNT} {COUNT:character:characters}".
• New Validator (利用できる with a Peter's More Validators license): RequiredSelectionValidator. When a 選択 is 要求するd on a 支配（する）／統制する that is not textual or 名簿（に載せる）／表（にあげる）. Supports ListView, DataIndex, DES's Calendar, MultiSelectionCalendar, MonthYearPicker, and TimePicker.
• In ASP.NET 2 and higher, an HttpHandler is now used to 配達する scripts and style sheets to the browser. It 取って代わるs the GetFiles.aspx とじ込み／提出する (although that remains as a backup 解答.) The Web 使用／適用 Updater will 追加する an 入ること／参加（者） in the <httpHandlers> section of your web.config とじ込み／提出する. When using IIS 7, the <system.webServer> section will need an 入ること／参加（者） in its <handlers> section. It will be 追加するd by the Web 使用／適用 Updater if the system.webServer section is 現在の. You will need to 追加する it manually if that section does not 存在する.
• MultipleRequiredControlsValidator now supports CheckBoxes and RadioButtons.
• New 所有物／資産／財産: DefaultErrorFormatterSkinID on PageManager and PeterBlum.DES.全世界のs.Page. Validators whose ErrorFormatterSkinID 所有物／資産／財産 is 始める，決める to "{DEFAULT}" will first look for a value in the DefaultErrorFormatterSkinID 所有物／資産／財産. If 割り当てるd, it is used as the SkinID. This feature also changes the default value for a validator's ErrorFormatterSkinID from "" to "{DEFAULT}". It will have no 衝撃 until you explicitly change the DefaultErrorFormatterSkinID.
• The ErrorFormatterSkinID and DefaultErrorFormatterSkinID 所有物／資産／財産s now let you 無視／無効 所有物／資産／財産s that it 宣言するs by using a syntax like ErrorFormatterSkinID="MyTextFormatter {陳列する，発揮する='dynamic'}".
  They also let you enter the 基準 指名するs of the errorformatters, like "text" and "texterrorformatter" to select their default value without having a saved errorformatter template in the custom.des.config とじ込み／提出する.
• The PageManager 支配（する）／統制する now supports the に引き続いて 所有物／資産／財産s: ControlErrorCssClass, ListErrorCssClass, CheckBoxErrorCssClass, TextHiliteFieldsCssClass, and NonTextHiliteFieldsCssClass. (They were always 利用できる programmatically on the PeterBlum.DES.全世界のs.Page 反対する.)
• New event on PeterBlum.DES.全世界のs.Page: Use the BeforeValidation event handler to run code first, each time the DESPage.実証する() method is called.
• The PeterBlum.DES.全世界のs.Page.PostPageValidationFunctionName 所有物／資産／財産 is used to call your own scripts すぐに after page-level validation occurs, whether it was valid or not.
• New 所有物／資産／財産 on FieldStateControllers: UpdateWhileEditing. 決定するs if the FieldStateController is 誘発する／引き起こすd as the 使用者 types into a textbox that it uses to 評価する its 条件. By default, it does not and only 誘発する／引き起こすs when 焦点（を合わせる） leaves the textbox. 始める，決める this to true to 評価する the FieldStateController with each keystroke.
• New 所有物／資産／財産 on SpecialDates 支配（する）／統制する: DayOfWeekConflictRule. 決定するs what happens when both a SpecialDayOfWeek and any other SpecialDate item 株 the same date. One of the two must be selected based on this 支配する.
• The Enabled 所有物／資産／財産 of the Calendar 支配（する）／統制する now will 妨げる changing the selected date when it is 無能にするd. The FieldStateController will visually update the Calendar as it toggles the Enabled 所有物／資産／財産.
• On Date and Time textboxes, you can turn off the AutoHint feature but still get the tooltip 体制／機構 with the text of the 自動車 hint. Call the 支配（する）／統制する's BuildDescriptionForHint() method in Page_Load. Make sure AutoHint is 誤った.
• New 所有物／資産／財産 on FilteredTextBox: UseKeyboardFiltering. 決定するs if the （弁護士の）依頼人-味方する filters out characters that are not supported by the datatype. This is usually left true unless you need to switch the 支配（する）／統制する between unfiltered and filtered.
• Web 使用／適用 Updater automatically 追加するs the <場所 path="DES"> tag to the web.config とじ込み／提出する. This is needed by 場所／位置s using Forms Authentication.
• Design 方式 速度(を上げる） in VS2005 and 2008 has been 改善するd when there are a large number of DES 支配（する）／統制するs on the design surface.
• Design 方式 support for the Visual Studio/VWD 命令（する）: "ASP.NET 非，不，無-Visual 支配（する）／統制するs". When unchecked, the に引き続いて 支配（する）／統制するs will be hidden from design 方式: PageManager, NativeControlExtender, SpecialDates, all FieldStateControllers, and CalculationController. FYI: The 命令（する） is under the 見解（をとる） menu. If not 設立する, you can 追加する it using the Customize 命令（する）.

• 予定 to changes in RadControls for ASP.NET AJAX Q1 2008, the Telerik_Web_UI.config とじ込み／提出する has been updated. Copy the one from the [DES 製品 folder]\Third Party Support\Telerik RadControls into the DES folder of your web 使用／適用. This とじ込み／提出する will still work with Q3 2007 too.
• Safari 3.1 did not 扱う clicks on popups 正確に when the popup was on a scrolled web page.
• The MonthYearTextBox would always 割り当てる this year to the date instead of the requested date when the ShortDatePattern was "d/MM/yyyy" or "dd/MM/yyyy".
• The MultiSelectionCalendar's Select Month button did nothing when on December of any year.
• Some cultures 陳列する，発揮するd "NaN" as the week 列／漕ぐ／騒動 number on the Calendar and MultiSelectionCalendar.
• When a CombinedErrorMessages 支配（する）／統制する uses the PopupErrorFormatter, there was a javascript error if the page 地位，任命するd 支援する and redrew with the 支配（する）／統制する showing an error.
• Only in v4.0.1: When AJAX is 体制／機構, you may get a NullReferenceException where the callstack 含むs "ControlInAJAXUpdate".
• This error shown by ASP.NET AJAX in an 警報 box no longer happens: "The script tag 登録（する）d for type 'ASP.page_aspx' and 重要な 'DES_ClientScripts' does not 含む／封じ込める any valid script tags."
• When using the CombinedErrorMessages 支配（する）／統制する within AJAX, a callback いつかs lost its ability to update validators after an edit. It still worked on a （弁護士の）依頼人-味方する 服従させる／提出する.
• The TimeOfDayTextBox and DurationTextBox did not 扱う their RoundUpMinutes 所有物／資産／財産 正確に.
• When using the AJAXManager's PreLoadForAJAX features, it now 負担s script とじ込み／提出するs and style sheets more intelligently in several 事例／患者s.
• The ValidationSummary did not appear when in a MultiView or Wizard, after the first 見解（をとる）.
• PopupTimePicker would always be 明白な so long as its BodyHeight 所有物／資産／財産 was 割り当てるd.
• When showing the toggle button on a Date or Time 支配（する）／統制する and you are using a FieldStateController to change the 支配（する）／統制する's enabled 明言する／公表する, postbacks いつかs resulted in the toggle button disappearing.
• The ChangeMonitor failed to 適用する changes made to the 現在の 明言する／公表する on the server 味方する after an AJAX callback.
• On postback, an Integer segment within the MultiSegmentDataEntry 支配（する）／統制する may 報告（する）／憶測 a validation error when it was 訂正する.
• When 変えるing from VAM to DES, the Web 使用／適用 Updater would 変える these style sheet class 指名するs incorrectly: VAMMultiSegTextBox and VAMMultiSegContainer. They should be DESTBMultiSegTextBox and DESTBMultiSegContainer.
• When using the app_GlobalResources folder but you need the String Lookup System to 接近 a database, strings were not returned from the database.
• When using the 拡大するd 所有物／資産／財産s Editor on the TimeOfDayTextBox, the TimePicker was not 申し込む／申し出d in the icons along the 最高の，を越す.

• Validation support for these Telerik RadControls "Prometheus" web 支配（する）／統制するs: RadEditor, RadComboBox, RadGrid, RadMenu, RadTextBox, RadNumericTextBox, RadMaskedBox, RadDateInput, and RadDatePicker.
  Run the Web 使用／適用 Updater's "任命する／導入する an update" 選択. It will 結局 名簿（に載せる）／表（にあげる） third party 支配（する）／統制するs. Make sure the first item is checked.
  See the Using Third Party 支配（する）／統制するs guide for 詳細（に述べる）s.
• Web 使用／適用 Updater: When you elect to manually 任命する／導入する 議会s (for the GAC), it now 追加するs the <assemblyBinding> and <追加する tagPrefix> tags.
• New 所有物／資産／財産: AcceptPeriodAsDecimalSeparator. On Decimal, 通貨, and パーセント TextBoxes. Lets cultures whose decimal separator is not a period to 受託する a period character in 新規加入 to their decimal separator. 広大な／多数の／重要な for numeric keypad 入ること／参加（者） of numbers.
• URL 所有物／資産／財産s that support images with 圧力（をかける）d and mouseover 見解／翻訳／版s now 受託する up to 3 URLs in this 麻薬を吸う (|) delimited 判型: normal|圧力（をかける）d|mouseover. When used, this 無視／無効s DES's 匂いをかぐing out image とじ込み／提出するs for 圧力（をかける）d and mouseover 見解／翻訳／版s. It also lets WebResource 使用者s support 圧力（をかける）d and mouseover images.
• EmailAddressValidator SmartTag now has 所有物／資産／財産s for MultipleAddressesAllowed, DelimiterCharacter, and DelimiterAllowsSpace.
• New 所有物／資産／財産: ShiftKeyForRange on MultiSelectionCalendar. By default, 使用者s can 持つ／拘留する 負かす／撃墜する the 転換 重要な to 延長する a 範囲. When you 始める，決める ShiftKeyForRange to 誤った, the 転換 重要な cannot create a 範囲. A click with the 転換 重要な 圧力（をかける）d will work the same as when it is not 圧力（をかける）d.
• Some new debugging 道具s let you 調査する AJAX, validation, the page, and more settings very quickly.
  See "調査するing the 現在の Settings" in the General Settings Guide.
• ImageButton supports images for 圧力（をかける）d and mouseover 影響s with the MultipleImages 所有物／資産／財産 and the ImageUrl 所有物／資産／財産's support of the 麻薬を吸う delimited 名簿（に載せる）／表（にあげる） of URLs.
• Buttons support an 代案／選択肢 style sheet class when 無能にするd with the WhenDisabledCssClass 所有物／資産／財産. ImageButton also supports an 代案／選択肢 image when 無能にするd with the WhenDisabledImageUrl 所有物／資産／財産.
• TextBox.ValueWhenBlankCssClass 所有物／資産／財産 now supports the "+" notation 許すing its style to 合併する with the 存在するing CssClass 所有物／資産／財産 instead of 無視／無効 it. This 保存するs styles from CssClass and only 無視／無効s the styles that are introduced in ValueWhenBlankCssClass.

• When the CombinedErrorMessages 支配（する）／統制する had its ErrorFormatter 始める，決める to Popup, the popup did not appear when 焦点（を合わせる） was on the field with the error. (It still appeared when the mouse was over the error icon.)
• DateTextBox gave a javascript error when 試みる／企てるing to open the calendar if the ASP.NET declarative syntax had any 所有物／資産／財産s in the <Calendar> section.
• When using the Popup Hint feature and your hint 含む／封じ込めるd a 二塁打 引用する, it would 生成する a javascript error. When the hint 含む／封じ込めるd a \ character, it would not appear in the PopupView.
• On 生産／産物 servers, this exception occurred occassionally: System.InvalidOperationException, " The instance is a duplicate of one already in the 名簿（に載せる）／表（にあげる）." Stack trace shows: "at PeterBlum.DES.CachedCombinedFiles.追加する(反対する pValue)"
• In cultures that use ASCII 160 to 代表する the thousands separator, that character was not 受託するd in the DecimalTextBox, CurrencyTextBox, and PercentTextBox. 含むs Finland and Sweden.
• For numeric textboxes. When using the MinValueToNative, MinValueToInteger, MinValueToDouble, or the max 見解／翻訳／版s of the same, if you 含むd the 通貨 symbol, パーセント symbol, or thousands separator on the textbox, you would get this exception: "支配（する）／統制する.MinValue is not an integer or decimal value."
• When a DateTextBox is 最初 無能にするd by a FieldStateController, upon getting enabled by the FSC, an 試みる／企てる to popup the calendar failed with a javascript error.
• DateTextBox and validators using DataType=Date would fail in cultures using upper ASCII and unicode characters. It had checked for A-Za-z as all letters, 行方不明の characters with umlats and for other languages.
• Bulgarian culture 追加するs extra text into its ShortDatePattern that 妨げるd DateTextBox and validators using DataType=Date from working.
• TimeOfDayTextBox and DurationTextBox incorrectly 扱うd cultures where the TimeSeparator character is "."
• When using ValueWhenBlankCssClass on a textbox with a RequiredTextField that was using PeterBlum.DES.全世界のs.Page.ControlErrorCssClass to change the textbox when it is in an error, ControlErrorCssClass should always 無視／無効 ValueWhenBlankCssClass. It did not 終始一貫して.

• Support for RadControls "Prometheus" 壇・綱領・公約. Please see the 指示／教授／教育s in the "Using these 支配（する）／統制するs with AJAX" section of the 使用者's Guide.
• Support for Infragistics AJAX-enabled 支配（する）／統制するs. The PDP 支配（する）／統制するs can be inside of a WebAsyncRequestPanel or UltraWebTab. Please see the 使用者's Guide for the section "Using Infragistics AJAX-enabled 支配（する）／統制するs" to 始める，決める up this feature.
• The ToolkitScriptManager 支配（する）／統制する from the AJAX 支配（する）／統制する Toolkit is supported.
• Some cultures use the 選び出す／独身 引用する (') character in the LongDatePattern to 保存する a literal string element. This is now supported.

• When the calendar is 陳列する，発揮するd in FireFox or other Mozilla-based browser, the 国境s for day 独房s where not shown so long as xWeekRowsCellSpacing=0 (the default). They are now shown.
• The DateTextBox.xClientParserFunctionName 所有物／資産／財産 原因（となる）d a javascript error when used after an AJAX callback.
• When you have two DateTextBoxes 体制／機構 in a 範囲 and both are using xAutoPopupOnFocusB=true, clicking in one textbox pops it up. Clicking in the second textbox popped up but の近くにd almost すぐに.
• When the DateTextBox is using xAutoPopupOnFocusB="True" on a 非，不，無-IE browser, the first click into the calendar after autopopup, の近くにs the calendar. It should only の近くに when selecting a date or clicking the 適用する button.
• When you have a MultiSelectionCalendar 始める，決める up to call PreLoadForAJAX(), it 生成するd a server 味方する error on a callback.
• MultiSelectionCalendar.GetSelectedDateRanges() method was not reliable and has been rewritten.
• MultiSelectionCalendar ignored a click on the Month toggle button during December of any year.
• When using the xExpandedDateFormatter 所有物／資産／財産 on a calendar that is within an AJAX update and the calendar is only shown after the callback, javascript errors occurred when 試みる／企てるing to show the ExpandedDateFormatter box.
• If you （疑いを）晴らす any of the predefined ContextMenus then 追加する a 選び出す／独身 命令（する）, you would get a javascript error when popping up the 状況 menu.
• When using Microsoft ASP.NET AJAX with VAM, Safari would not 扱う callbacks 適切に. It 行為／法令／行動するd like AJAX features were never 体制／機構.
• The DateTextBoxCompareValidator would not compare 正確に when the 現在の culture has a ShortDatePattern with a 選び出す／独身 M or D (m/d/yyyy would fail). Only 影響する／感情d the （弁護士の）依頼人-味方する evaluation. Server 味方する worked.

• The ToolkitScriptManager 支配（する）／統制する from the AJAX 支配（する）／統制する Toolkit is supported.
• An AJAX Callback いつかs should 回復する the 明言する／公表する of validators to show their error messages. Other times it should not. You can now 支配（する）／統制する this with the PeterBlum.VAM.AJAXManager.現在の.RestoreValidatorState 所有物／資産／財産. It defaults to true, 回復するing validator error messages after the callback.
• 付加 弁護s for 最近の Script 注射 attack シナリオs. Be sure to 取って代わる the master.config とじ込み／提出する in the \VAM\VISE Config とじ込み／提出するs folder with the new one.
• String Lookup System now can retrieve a 関係 String from the <connectionstrings> section of the web.config とじ込み／提出する as an 代案／選択肢 to defining the string within the custom.vam.config とじ込み／提出する. Use the ConnectionStringName 所有物／資産／財産 in the <StringLookup&;gt; section of the custom.vam.config とじ込み／提出する.

• When using the PeterBlum.VAM.全世界のs.Page.ShowAlertOnSubmit and you have a validator that uses OverrideClientScriptEvaluation = Hide or HideOnSubmit, the 警報 shown after 服従させる／提出する did not 含む that validators 要約 error message.
• The ASP.NET 2 支配（する）／統制する HiddenField was not fully supported. Validators that 評価するd it would ignore its value.
• The CountTrueConditionsValidator did not 割り当てる the 訂正する value to the {COUNT} 記念品 when doing server 味方する validation.
• When using the NoErrorFormatter and Enabler 所有物／資産／財産s of the Validator, if the Enabler 無能にするs the validator, the NoErrorFormatter showed its image. It should be hidden.
• When using the ToolTip 所有物／資産／財産 of the RequiredFieldMarker or RequiredFieldDescription 支配（する）／統制する and you have an embedded image, the tooltip was 取って代わるd by the 代案／選択肢 text when the mouse is over the image in Internet Explorer. It should show the ToolTip 所有物／資産／財産 value.
• When using Telerik Prometheus v2007.2.918.0, a callback could 報告（する）／憶測 an "Sys.WebForms.PageRequestManagerParserErrorException" error through a （弁護士の）依頼人-味方する messagebox. This only happens on the first page request since the 使用／適用 starts up.
• When a FieldStateController (or 類似の 支配（する）／統制する) is in the 列／漕ぐ／騒動 of a grid and that 列／漕ぐ／騒動 is 削除するd because of a DataBind on postback, a javascript error いつかs occurred on the （弁護士の）依頼人-味方する.
• When using Microsoft ASP.NET AJAX with VAM, Safari would not 扱う callbacks 適切に. It 行為／法令／行動するd like AJAX features were never 体制／機構.
• CurrencyTextBox, DecimalTextBox, and validators whose DataType 所有物／資産／財産 is 始める，決める to 二塁打 or 通貨 had （弁護士の）依頼人-味方する errors when the decimal number had 7 or more digits after the decimal point.
• When a page 含むs server 味方する only validators that show their error messages in the ValidationSummary, the ValidationSummary uses its ScrollIntoView 所有物／資産／財産 and the 服従させる／提出する button uses the MayMoveOnClick 所有物／資産／財産, a click on the 服従させる／提出する button when the page is valid may not 服従させる／提出する.
• When using the Button's DisableOnSubmit 所有物／資産／財産 and that button is created within an AJAX Callback with its Enabled 所有物／資産／財産 始める，決める to 誤った, it would be enabled when 陳列する，発揮するd.

• Support for RadControls "Prometheus" 壇・綱領・公約. If using RadAJAX, just call the PeterBlum.VAM.AJAXManager.UsingRadAJAX() method but pass in the ScriptManager instead of the RadAjaxManager.
• Support for Infragistics AJAX-enabled 支配（する）／統制するs. The PDP 支配（する）／統制するs can be inside of a WebAsyncRequestPanel or UltraWebTab. Please see the 使用者's Guide for the section "Using Infragistics AJAX-enabled 支配（する）／統制するs" to 始める，決める up this feature.

• Broken in 3.0.9: The Group 所有物／資産／財産 on individual validators failed to 供給する server 味方する validation when it 含むd the 麻薬を吸う character ("|").
• If you explicitly called PeterBlum.VAM.全世界のs.Page.ValidateGroup(), it would not 適切に update the ValidationSummary of the same group 指名する.
• When using AJAX to manage DetailView 支配（する）／統制する that 含む／封じ込めるs VAM 支配（する）／統制するs, a javascript error occurred if any VAM 支配（する）／統制するs were outside of the AJAX call and 位置を示すd earlier on the page.
• When using the CombinedErrorMessages 支配（する）／統制する with a validator whose ErrorFormatterSkinID is 体制／機構, the skinID would 許す the validator to show its error message instead of just letting the CombinedErrorMessages 支配（する）／統制する do it.
• When using AJAX, the 無能にする on 服従させる／提出する feature (Button.DisableOnSubmit) いつかs buttons 無能にするd. This was a タイミング 問題／発行する where the AJAX 処理／取引 was faster than 0.02 of a second.
• When AJAX updates validators that are showing their errors on the page, those validators would hide their errors as they were reloaded. They now 回復する to their 明言する／公表する 事前の to the callback.
• In Visual Studio 2005 design 方式, if a validator was within 確かな 支配（する）／統制するs and you visually resized the 支配（する）／統制する, you would get an error.
• When using a CalculationController that has a ConditionCalcItem within an AJAX callback, a javascript error occured after the callback.
• When using the validator's Blink feature, if validators are blinking and a callback occurs, a javascript error may occur (タイミング 問題／発行する).

• Support for v1 of MS ASP.NET AJAX.
• New （弁護士の）依頼人-味方する 機能（する）／行事s for the MultiSelectionCalendar: MSC_GetRange() and MSC_GetSelectedCount(). MSC_GetRange gets either the lowest or highest selected date. MSC_GetSelectedCount() gets the number of selected items.
• MultiSelectionCalendar has a new 所有物／資産／財産, xUnselectOthersFirstB. When true, it always unselects other dates when the 使用者 試みる／企てるs to make a new 選択. It does not toggle dates. Use it to 施行する a 支配する where you 許す 1 day, 1 week, or 1 month, but no other types of 範囲s.
• Support for subclasses of the MS ASP.NET AJAX 支配（する）／統制するs: ScriptManager and UpdatePanel in the AJAXManager.UsingMicrosoftAJAX() and RegisterUpdatePanel() methods.
• MonthYearTextBox now supports the xDateFormat 所有物／資産／財産, 許すing abbreviated and long months.

• MonthYearTextBox 割り当てるd the wrong min-max date 範囲 to its popup MonthYearPicker. It was off by one month.
• MultiSelectionCalendar can 報告（する）／憶測 a javascript error when the mouse passes over it if TrueBrowser.xSupportsCalendarB=誤った.
• Some cultures put the AM/PM Designator before the time, such as in Korea, where the LongTimePattern is "tt hh:mm:ss". The TimeOfDayTextBox now supports that positioning of the AM/PM Designator.
• When using the SpecialDates 支配（する）／統制する within MS ASP.NET AJAX RC 1 or later, callbacks invoked by the UpdatePanel did not get updated SpecialDate data.
• When the DateTextBox has today's date outside of the 範囲 of xMinDate and xMaxDate and the 使用者 pops up the calendar with an empty datetextbox, it shows the month that 含む／封じ込めるs today's date. While that is 普通は 罰金, when today's date is at least one month outside of the 範囲, the popped up month will be blank. It now adjusts to show either the first or last month of the 範囲.
• When using VS2005 with its 絶対の positioning feature in design 方式, you could not drag most of the 支配（する）／統制するs to position them.
• When using xShowWeekendDaysB=誤った in the DateTextBox's popup calendar, the 週末s were still shown, except in the day of week header.
• The MultiSelectionCalendar did not 保存する the xSelectedDates 所有物／資産／財産 in the ViewState. This 影響する／感情d it when it was made invisible then 回復するd to visibility, such as in a Wizard 支配（する）／統制する. Since the xSelectedDates 所有物／資産／財産 消費するs a larger than normal 量 of the ViewState (given an 広範囲にわたる 名簿（に載せる）／表（にあげる） of 大（公）使館員d dates), this data is only written into the ViewState when the 支配（する）／統制する is invisible. It has no 衝撃 when 明白な.
• When the MultiSelectionCalendar was made invisible then 回復するd to visibility through a postback, this exception would occur: "The hidden field [ID]_SelDates is 行方不明の or has been tampered with."
• When using the PopupEffect and the 支配（する）／統制する has a style sheet class that defines a filter style, a javascript error occurred.
• When using VAM's DataTypeCheckValidator on a TimeOfDayTextBox that is connected to a DateTextBox, the （弁護士の）依頼人-味方する validation would 許す times above 24 hours. It should not consider that a valid time of day.
• The MonthYearTextBox had the xAutoPopupOnFocusB 所有物／資産／財産. It should not be on that 支配（する）／統制する. If 割り当てるd, it would 原因（となる） a javascript error when 焦点（を合わせる） is 始める，決める to the MYTB.
• Setting the 所有物／資産／財産 DateTextBox.xPopupCalendar.xUsePopupEffectB to 誤った did not 無能にする the 影響.
• When the TimePicker has only one time value, a javascript error occurred.
• In VS2005, if you edit the PopupCalendar 支配（する）／統制する's xCalendar 所有物／資産／財産 in the 所有物／資産／財産s Editor, the contents between the start and end <date:PopupCalendar> tags 生産（高） the wrong info: 鮮明度／定義s of a label, image, and button.
• When using the TimeTextBoxCompareValidator and you forget to 割り当てる the ControlToCompare 所有物／資産／財産, a （弁護士の）依頼人-味方する error may occur.
• Introduced in 2.0.3: When the DateTextBox used xDateFormat of Abbreviated or Long, there could be clean 味方する validation errors on a valid date. Only occurred when the xDateTimeFormatInfo.LongDatePattern 含む／封じ込めるd "dddd" or "ddd".

• Support for v1 of MS ASP.NET AJAX.
• MultiSegmentDataEntry 支配（する）／統制する now 陳列する，発揮するs its Text and TextNoSeparators 所有物／資産／財産s in the design 方式 道具 for setting up databindings. (These 所有物／資産／財産s now have the BindableAttribute.)
• The SelectedIndexValidator and SelectedIndexCondition now 正確に support matching the 索引 in a 多重の 選択 listbox. 以前 they only matched to the first selected listitem.
• Support for subclasses of the MS ASP.NET AJAX 支配（する）／統制するs: ScriptManager and UpdatePanel in the AJAXManager.UsingMicrosoftAJAX() and RegisterUpdatePanel() methods.
• Support for Telerik RadMenu v4. See the Using rad 支配（する）／統制するs Guide.pdf in [VAM 製品 folder]\Third Party Support\Telerik r.a.d. 支配（する）／統制するs. If you update to Telerik RadMenu v4, you must 修正する VAM to use a different 議会 and new 体制／機構 指示／教授／教育s.

• If an IgnoreConditionValidator or ValidationSummary.AddMessage() call 追加するd an error message to the ValidationSummary during an AJAX callback, that error message would remain in the ValidationSummary after later postbacks. It should be 除去するd (have a life of one callback.)
• CurrencyTextBox 報告（する）／憶測d validation errors with the DataTypeCheckValidator when using cultures that have a 非，不，無-breaking space character (ASCII 160) as the thousands separator. This 含むs fr-CA and sv-SE.
• Introduced in 3.0.8: Some 所有物／資産／財産s Grids that 申し込む／申し出 a 選ぶ 名簿（に載せる）／表（にあげる） of 支配（する）／統制するs 設立する on the page would have a blank 名簿（に載せる）／表（にあげる）.
• The MultiSegmentDataEntry.TabOnEnterKey 所有物／資産／財産 was not supported on DropDownListSegments. It is now.
• Using the FSCOnCommand and MultiFSCOnCommand 支配（する）／統制するs: When the FieldValue or InnerHTMLState 所有物／資産／財産s are 割り当てるd to a textual value and that value matches the 初期の value of the ControlIDToChange, they were ignored. They should always 適用する their value.
• On pages with validators, the form tag's onreset せいにする would grow with each 地位，任命する 支援する. The same script was getting 合併するd over and over.
• The Group 所有物／資産／財産 on validators did not work 正確に in ASP.NET 2 when the validator was in a nested 指名するing コンテナ.
• When the Group 所有物／資産／財産 was used on an IgnoreConditionValidator with the "+" 記念品, it would throw an exception at runtime.
• When a CombinedErrorMessages 支配（する）／統制する uses the NoErrorFormatter with the 方式 of 実証するd and there are several on the page, a 実証するd field showed the NoErrorFormatter to the 使用者 on all of the CombinedErrorMessages 支配（する）／統制するs.
• When a validator 含む／封じ込めるs a "runtime 記念品" in its SummaryErrorMessage but not in its ErrorMessage, the ValidationSummary did not 変える that 記念品 into its value. It stayed the 記念品.
• When using the Button's DisableOnSubmit 所有物／資産／財産 with an AJAX update, buttons that were 無能にするd 事前の to 服従させる／提出する are re-enabled after postback. They should have remained 無能にするd.
• When using the PeterBlum.VAM.全世界のs.Page.RegisterCallbackControl() method, the Group 所有物／資産／財産 was ignored. It always used the group "".
• MultiFieldStateController and MultiFSCOnCommand ignored the Enabler 所有物／資産／財産.
• When using the Web 使用／適用 事業／計画（する） feature of VS2005 to develop a web 使用／適用, graphics and style sheets did not get 適用するd in design 方式.
• In some 事例／患者s, when a VAM 支配（する）／統制する is searching for a 支配（する）／統制する by its ID and that 支配（する）／統制する is in an ancestor NamingContainer, it would not be 設立する.

• Support for Microsoft ASP.NET AJAX 解放（する） 候補者 1.
• VAM's TextBoxes now support the TextMode=Password when using the TabOnMaxLength 所有物／資産／財産.
• When using the AJAXManager.RegisterUpdatePanel() method with 多重の UpdatePanels, the first UpdatePanel's UpdateMode must be 始める，決める to Always or else other パネル盤s will not refresh their scripts, breaking them after a callback. The RegisterUpdatePanel() method has been 高めるd to automatically 始める，決める the first UpdatePanel to UpdateMode=Always.
• When a VAM TextBox uses the ValueWhenBlank feature, 以前 validators needed to do extra 体制／機構 to ignore the ValueWhenBlank in the textbox. Now its (a)自動的な／(n)自動拳銃. Your RequiredTextValidator no longer to 明示する the ValueWhenBlank in its UnassignedValues 所有物／資産／財産 and others do not need to 設立する an Enabler 反対する. (If they continue to do so, it is 害のない.)
• Support for Infragistics WebGrid from their 2006 解放（する）s. There was a change to their code that broke my 存在するing support. VAM has updated UWGClasses code とじ込み／提出するs ([製品 folder]\third party support\Infragistics WebGrid). 取って代わる the 現在の とじ込み／提出する in your web app with the 最新の. It will continue to work with older 見解／翻訳／版s of WebGrid. In 新規加入 the Connect() method now optionally 許すs 軽く押す／注意を引くing the position of the validator with pXOffset and pYOffset parameters. These are 文書d in "Using Infragistics WebGrid Guide.pdf".

• Better support for Internet Explorer 7. 事前の to this 解放（する）, some （弁護士の）依頼人-味方する features would work 異なって from IE 6.
• AJAX/Callbacks: When using AJAX callbacks with a VAM Button or ImageButton, CausesValidation was always 扱う／治療するd at true, even when it was 誤った.
• AJAX/Callbacks: When using the radAJAXPanel with the AJAXManager.UsingRadAJAX() method, callbacks did not work for FireFox and other Mozilla browsers.
• AJAX/Callbacks: When a FieldStateController is used to change visibility inside of an MS AJAX UpdatePanel, it cannot make the element 明白な after a callback.
• AJAX/Callbacks and ASP.NET 2.0 only: when using Server.移転 to move away from a page that you were using the AJAXManager would result in a javascript error on the 目的地 page.
• AJAX/Callbacks: After an AJAX callback, any validator that has a SummaryErrorMessage did not show that error message in a ValidationSummary that appears later on the page. It either showed the ErrorMessage 所有物／資産／財産 or if that 所有物／資産／財産 was blank, it was not shown.
• AJAX/Callbacks: When using a MultiConditionValidator or MultiCondition 反対する with an AJAX callback on the page, the callback will result in a （弁護士の）依頼人-味方する Stack 洪水 error.
• AJAX/Callbacks: When using Atlas and the page has Peter's Date 一括 支配（する）／統制するs using VAM's validators, the javascript for any VAM 支配（する）／統制するs 伴う／関わるd in the callback would not be 体制／機構. (It appears to be a bug in Atlas but VAM has a 切り開く／タクシー／不正アクセス to 避ける it.)
• Introduced in 3.0.6: When using PeterBlum.VAM.全世界のs.Page.RegisterKeyClicksControl() and there is no VAM textbox on the page, a javascript error occurred.
• Introduced in 3.0.6: When using the radMenu or radTabStrip 支配（する）／統制する (from radControls) with VAM, the （弁護士の）依頼人-味方する script never stopped an 活動／戦闘 予定 to an 無効の validator.
• Introduced in 3.0.6: When using any VAM TextBox with the CustomKeyDownFunctionName or CustomKeyPressFunctionName 所有物／資産／財産s, the 使用者 would get a javascript error when typing into the textbox.
• Introduced in 3.0.6: When the CalculationController or any type of FieldStateController is in a FormView 支配（する）／統制する, design 方式 will show an "反対する 言及／関連 not 始める，決める to an instance of an 反対する."
• The HyperlinkErrorFormatter needed to support the 回復するing animated GIFs after you clicked it. (拡大 of the feature 追加するd in 3.0.7.)
• When using the ValidationSummary or PeterBlum.VAM.全世界のs.Page.ShowAlertOnSubmit features on a page with 多重の validation groups, if a MultiConditionValidator is in one of those groups, it's error message could appear in the ValidationSummary or 警報 of the wrong group.
• 設立する and 直す／買収する，八百長をするd a memory 漏れる connected to the "ValidatorAction" and "ErrorFormatter" class.
• When these 支配（する）／統制するs are 追加するd into an ASP.NET 2 CompositeControl class, any 所有物／資産／財産 that 減少（する）s 負かす／撃墜する to show a 名簿（に載せる）／表（にあげる） of 支配（する）／統制するs already on the page would throw a NullReferenceException.
• When the page has javascript 無能にするd (PeterBlum.VAM.全世界のs.Page.JavaScriptEnabled=誤った), several AJAX features still 生産（高） their scripts.
• ASP.NET 2 only: When the VAM LinkButton uses the WebForm_DoPostBack() 機能（する）／行事 for its onclick event, it 生成するd script errors when clicked.

• Support for Microsoft ASP.NET AJAX 解放（する） 候補者 1.
• The MultiSelectionCalendar 申し込む／申し出s these new 所有物／資産／財産s, xFirstSelectedDate and xLastSelectedDate, to return the first and last dates in the selected dates data.
• The MultiSelectionCalendar 申し込む／申し出s the GetSelectedDateRanges() method to return all selected date 範囲s 設立する within the selected dates data.
• The DateTextBox's Custom Parser now can 示す that the value passed is 違法な and should not be 受託するd by returning 誤った.
• New javascript 機能（する）／行事, MSC_SetRange, is 利用できる on the MultiSelectionCalendar. Use it to 追加する your own buttons 近づく the calendar that also can select, unselect or toggle a 範囲. The MultiSelectionCalendar 支配（する）／統制する introduces a 関係のある method, GetSelectRangeScript(), to easily create calls to MSC_Range.
• New javascript 機能（する）／行事, MSC_GetLastDateClicked, is 利用できる on the MultiSelectionCalendar. Use it to return the date of the last 独房 that was selected or unselected.
• 以前, you could not get the 地位，任命するd 支援する selected date value from CS_Calendar.xSelectedDate inside Page_Load(). Now you can.
• Better support for 代案／選択肢 HttpHandlers 含むing SharePoint.
• 追加するd the event SpecialDates.OnReviewSpecialDateItem. It is called for each Special Dates item 反対する that was 追加するd through databinding. It 許すs you to その上の 修正する these 反対するs.
• The Special Date item and TimeRow classes (used by SpecialDates) now 申し込む／申し出s the 所有物／資産／財産 xDataSourceRow. It is 体制／機構 when databinding to 含む／封じ込める a 言及／関連 to the 列／漕ぐ／騒動 反対する that 供給するd the data used to create this 反対する. You can use it in the SpecialDates.OnReviewSpecialDateItem event to 修正する the Special Date item and TimeRow 反対する with data that isn't 直接／まっすぐに supported by the databinding features of SpecialDates.
• The CS_Calendar.xDayCellFormatter now 申し込む／申し出s the 所有物／資産／財産 xTooltipTemplate. Use it to 決定する the contents of the tooltip shown on date 独房s, or to 除去する that tooltip.
• The CS_Calendar.xDayCellFormatter and xExpandedDateFormatter 申し込む／申し出 a new 所有物／資産／財産 on their xDescriptionFormatter, xBody. It defines the formatting for the 団体／死体 of the 独房 to 許す 広範囲にわたる customization.

• When using the radAJAXPanel with the AJAXManager.UsingRadAJAX() method, callbacks did not work for FireFox and other Mozilla browsers.
• Better support for Internet Explorer 7. 事前の to this 解放（する）, some （弁護士の）依頼人-味方する features would work 異なって from IE 6.
• When VAM is also running, CS_Calendar would not 陳列する，発揮する the SpecialDates after a postback, on the 初期の month shown. It would update if you moved to another month.
• Text 入ること／参加（者） into the DateTextBox should have permitted the date separator character when using xDateFormat=Abbreviated or Long. Now it does.
• Use of the CSC_GetDateString() 機能（する）／行事 always failed with a javascript error.
• When the DateTextBox is 無能にするd through the FieldStateController or other （弁護士の）依頼人-味方する code, clicking the calendar button still opened the calendar, often with dates showing 99s.
• When using the TimeRows feature of SpecialDates to show time 列／漕ぐ／騒動s in the calendar, the TimeRows.xCssClass 所有物／資産／財産 was ignored.
• MultipleSelectionCalendar with the Toggle month button 利用できる selects the wrong dates when pointing to a calendar showing December.
• When these 支配（する）／統制するs are 追加するd into an ASP.NET 2 CompositeControl class, in the 所有物／資産／財産s Editor, any 所有物／資産／財産 that 減少（する）s 負かす／撃墜する to show a 名簿（に載せる）／表（にあげる） of 支配（する）／統制するs already on the page would throw a NullReferenceException.
• When using the UnselectableDatesValidator with an unselectable date that has no value in its xLabel 所有物／資産／財産, the server-味方する 生成するd ValidationSummary will omit its error message when UnselectableDatesValidator.xNoLabelErrorMessage is blank.
• When using PDP with VAM through the PeterBlum.PDPtoVAM.dll 議会, callbacks could fail with javascript errors when the PDP 支配（する）／統制するs are first 追加するd to the page after the callback.
• When using the MultiSelectionCalendar with xWeekendBackground 体制／機構, a click on a 週末 date to select did not visually show that 選択.
• When DateTextBox.xDateFormat is Abbrev or Long, if the xDateTimeFormatInfo.ShortDatePattern is a different order for D/M/Y compared to LongDatePattern, there would be validation errors.

• Support for Microsoft's AJAX Library (the beta 見解／翻訳／版s of "Atlas"). 予定 to some breaking changes between Atlas and the AJAX Library, Atlas 使用者s must use a わずかに different approach for using Peter's Date 一括 支配（する）／統制するs inside the UpdatePanel.
• CS_Calendar 含むs a new 所有物／資産／財産: xMultiMonthFullSpecialDateFormattingB. When using SpecialDates to 判型 date 独房s, this 決定するs what happens to date 独房s shown on one month but a part of another month that is also shown. When 誤った, those 独房s do not use the SpecialDates formatting. When true, they do. In previous 解放（する）s, the calendar does not show the formatting.
• BREAKING CHANGE: SpecialDates has a new 所有物／資産／財産, xHTMLEncodeDataFields. It is only used when reading from a DataSource. When true, it 適用するs HTMLEncoding to all string-type values. It defaults to true. 始める，決める it to 誤った to embed HTML tags and characters 設立する in the data source into the page. If you 以前 始める，決める this up with HTML in your data source, you MUST 始める，決める xHTMLEncodeDataFields to 誤った.
• When reading from a DataSource, all string types will have embedded carriage returns and line 料金d 変えるd into the <br /> tag automatically. 公式文書，認める that the xHTMLEncodeDataFields 所有物／資産／財産 does not have any 影響する／感情 on this.
• UnselectableDatesValidator did not support embedded web 支配（する）／統制するs for its error message. It now does.

• The textbox 支配（する）／統制するs ignored the TabIndex 所有物／資産／財産.
• When the TimePicker is used inside of a 指名するing コンテナ other than the Page 反対する (such as a UserControl or form using a MasterPage), after a postback, a javascript error occurred. This 影響する／感情d the TimeOfDayTextBox and DurationTextBox, PopupTimePicker and TimePicker.
• When the first DateTextBox or MonthYearTextBox on the page has xShowPopupB=誤った and any other on the page has xShowPopupB=true, the popup calendar would not appear. (A javascript error occurs when you clicked on the toggle button.)
• When the Calendar is using multi month 見解（をとる）, xAutoPostBackOnSelectionChangeB=true, and is 伴う／関わるd in an AJAX callback, after the callback 完全にするs, the calendar changed the first 見解（をとる）d month to the month you clicked in. It should not have changed the 見解（をとる）d months.
• When using the calendar's xDayCellFormatter, you can use 記念品s like {LABEL} and {DESC}. These 記念品s were not supported in the xDayNumberFormatting 所有物／資産／財産 or the Custom formatter's xOpeningHTML or xClosingHTML 所有物／資産／財産s. Now they are.
• When using the SpecialDates 支配（する）／統制する with TimeRows defined, if a TimeRow has no data to 陳列する，発揮する, a javascript error could occur.
• The Hungarian culture (id=hu-HU) 供給するs a ShortDatePattern with a period followed by a space as the date separator. This 原因（となる）d data 入ること／参加（者） errors in the DateTextBox. Now the code will 除去する the space, 限界ing the separator to just the period. This 直す／買収する，八百長をするs the errors.
• When using the TimeOfDayTextBox and a TimeOfDayValidator, it would not 報告（する）／憶測 an error when the hours were 24 or higher. The 新規加入 of the TimeOfDayMinMaxValidator would 報告（する）／憶測 the error but with a TimeOfDayTextBox, that should not be needed to catch times 越えるing 24 hours.

• Support for the Microsoft AJAX Library Beta 1. This 供給するs compatibility when using the UpdatePanel 支配（する）／統制する. Follow the directions in the "Using these 支配（する）／統制するs with AJAX" in each 使用者's Guide.
• VAM's LinkButton 支配（する）／統制する now 申し込む／申し出s the MayMoveOnClick 所有物／資産／財産 that was introduced on the other Buttons in VAM 3.0.6. It has a 制限: it doesn't work on any Mozilla-based browser or any that do not 申し込む／申し出 a click() method on the <a> tag.
• The CharacterValidator, CharacterCondition and FilteredTextBox 申し込む／申し出 several new 所有物／資産／財産s that categorize 関係のある groups of characters. They are DiacriticLetters (含むing ASCII and UNICODE), Punctuation, MathSymbols, CurrencySymbols, EnclosureSymbols (like brackets), and VariousSymbols. They 減ずる the need to 始める，決める up 名簿（に載せる）／表（にあげる）s of characters in the OtherCharacters 所有物／資産／財産s.

• After an AJAX update, any IntegerTextBox, DecimalTextBox and CurrencyTextBox that was 含むd in the update lost its 能力 to reformat when the 使用者 made an edit.
• When no validators are defined, a page that uses VAM's 始める，決める 焦点（を合わせる） to next 支配（する）／統制する 能力, 設立する in VAM's TextBoxes and MultiSegmentDataEntry 支配（する）／統制する, did not 前進する to the next 支配（する）／統制する.

• All 支配（する）／統制するs have been 高めるd to work within さまざまな AJAX 枠組みs, 含むing Microsoft Atlas, radAjax, and MagicAJAX. Configuration is 要求するd to get these 支配（する）／統制するs to work, 含むing calling a method on the new PeterBlum.VAM.AJAXManager 反対する and setting the InAJAXUpdate 所有物／資産／財産 on each 支配（する）／統制する. 詳細（に述べる）d steps are 供給するd in the "Using these 支配（する）／統制するs with AJAX" section of each 使用者's Guide.
• Internet Explorer 普通は stops animated GIFs as soon as the form.服従させる／提出する() 機能（する）／行事 runs. A clever 切り開く／タクシー／不正アクセス 設立する in this 会議 地位，任命するing http://会議s.asp.逮捕する/thread/1381507.aspx solves that and has been 器具／実施するd in VAM. It will run when any code 実証するs as the page is submitted. VAM Buttons that have CausesValidation=誤った will also run submission. For any other 状況／情勢, 令状 javascript code to call VAM_Reanimate(); in your onclick event that 服従させる／提出するs the page.
• New 所有物／資産／財産 on VAM's Button and ImageButton: MayMoveOnClick. When true, it 任命する／導入するs code that 妨げるs having the 使用者 to click twice on the button to 服従させる／提出する the page, if the button moved after the mouse 負かす／撃墜する on the 支配（する）／統制する.
• The に引き続いて 所有物／資産／財産s on PeterBlum.VAM.全世界のs.Page have 付加 functionality: TextHiliteFieldsCssClass, NonTextHiliteFieldsCssClass, ControlErrorCssClass, ListErrorCssClass, and CheckErrorCssClass. 以前 they always 取って代わるd the 存在するing style on the associated 支配（する）／統制する. That would 敗北・負かす styles that 含む／封じ込めるd width and 高さ settings. Now you can use a "+" character before the class 指名する and it will 保存する the 初めの class's styles. It 効果的に 合併するs the two classes together.
• BREAKING CHANGE. The EmailAddressValidator and 条件 now 妨げる any 付加 text after a valid email 演説（する）／住所 unless you 始める，決める the 所有物／資産／財産 AllowExtraText to true. 以前 it always 許すd extra text.
• Visual Input 安全 now knows to ignore the hidden field "__EVENTVALIDATION" which is 追加するd in ASP.NET 2.0. "__EVENTVALIDATION" is another 安全 手段 within ASP.NET and has its own validation system.

• XHTML 同意／服従 直す／買収する，八百長をする for ASP.NET 2.0. ErrorFormatter.ImageAlign 所有物／資産／財産 did not 生成する XHTML compliant code.
• The CountTrueConditionsValidator's server 味方する evaluation would incorrectly count a 条件 that 評価するd as "Cannot 評価する". It should not have counted it.
• The FSCOnCommand and MultiFSCOnCommand 支配（する）／統制するs can 原因（となる） a NullReferenceException on a postback that 試みる／企てるs to 実証する.
• When using a RequiredListValidator or RequiredListCondition with a RadioButtonList and the UnassignedIndex 所有物／資産／財産 is used, it ignored the value of UnassignedIndex in （弁護士の）依頼人-味方する validation.
• The ABARoutingNumberValidator should have 報告（する）／憶測d an error when you enter '000000000'. It did not.

• The MultipleSelectionCalendar now interactively 最高潮の場面s day 独房s that are going to be selected in 範囲. If you click on toggle week, day of week or month, it will 最高潮の場面 独房s too. This 行為 is the default. If you don't like the color choices, change them in the xHiliteRangeSelectColor and xHiliteRangeUnselectColor 所有物／資産／財産s.
• Support for MagicAJAX, a 解放する／自由な AJAX 枠組み.
• 拡張s to the AJAXManager to support a new 部類 of AJAX 製品s, from which MagicAJAX support was created. It 追加するs the new AJAXSystemType, GetScriptsAtEnd. It 供給するs you with 付加 選択s when 試みる／企てるing to get a third party AJAX system to work.
• When using 多重の Month 見解（をとる） in the Calendar and there are date 独房s to be formatted by the SpecialDates 支配（する）／統制する, v2.0.0 did not use the SpecialDates data when those Date 独房s were in the "other month" 独房s of the 現在の month. This 支配する 存在するs so that two months don't show 同一の info. This 支配する has been 修正するd so that the first month will show special dates from the earlier month and the last month will show special dates from the later month.

• The PetersDatePackage.dll 生成するd a 安全 Exception when placed into a 場所／位置 that has 安全 制限s through 部分的な／不平等な 信用. This was 予定 to the Best Order button appearing in VS.逮捕する's 所有物／資産／財産s Window. The button has been 除去するd, 許すing you to （軍隊を）展開する，配備する the PetersDatePackage.dll. The Best Order button still remains part of the 拡大するd 所有物／資産／財産s Editor dialog box. You can still get 安全 exceptions for other 推論する／理由s in a 部分的な／不平等な 信用 環境. See "任命する／導入するing into a 部分的な／不平等な 信用 環境" in the 取り付け・設備 Guide.
• The MultipleSelectionCalendar selected one date in the next month when using the toggle Day Of Week button in some 事例／患者s.
• ASP.NET 2.0: When using the <%= PeterBlum.PetersDatePackage.CommonFunctions.GetStyleSheetLinkTags(Page) %> tag and the <長，率いる> tag does not 含む／封じ込める a runat='server' 所有物／資産／財産, no style sheets were 追加するd at runtime.
• The Week 列／漕ぐ／騒動s area of a calendar いつかs positioned its 権利 辛勝する／優位 incorrectly. It may have been far to the left of the 国境 or crossed over the 国境. This problem depended on the browser. Only IE worked 正確に.
• In IE for Windows, the month change buttons on the 権利 味方する of the calendar had a bigger distance to the calendar's 国境 than the left 味方する. Same with buttons in the footer. They should have been equal distances.
• In Safari, the Multi Month 見解（をとる） did not draw in any month except the first. It showed the days of the last month in the first month's position.
• In most browsers other than Mozilla/FireFox, the calendar did not have a 国境 along the 最高の，を越す 列／漕ぐ／騒動 of Day 独房s, separating them from the day of week 指名するs. This happened when the xWeekRowCellSpacing 所有物／資産／財産 is "0". It now has a 国境.
• 確かな 見解／翻訳／版s of オペラ and Safari positioned the popup calendar incorrectly (usually to far left and up). While its not 100% perfect now, they do position better in most 事例／患者s.
• When typing into the DateTextBox and xDateFormat is Abbreviated or Long, if the 使用者 typed "/", the 状況 menu appeared. It should not because the "/" character should be 許すd for date 入ること／参加（者）. In 新規加入, selecting menu 命令（する）s at that time may have 生成するd a javascript error.
• When both the DateTextBox and MonthYearTextBox are on the page, popup the MonthYearPicker on the MYTB and click its 承認する button. It gave a javascript error.
• If the TimePicker had an empty xItems collection, it threw this exception: "Do not call OutputScriptInRender unless you call OutputScriptInPreRender from the OnPreRender method.".
• When using these 支配（する）／統制するs in AJAX and you called the PreLoadForAJAX(), if they were using any of the PopupOnMouseOverB 所有物／資産／財産s, a javascript error appeared as the page is 負担d.
• When the calendar is shown and has a xMaxDate setting, the date 独房 associated with xMaxDate did not have a 権利 国境 when xWeekRowsCellSpacing=0 on IE.
• When using 多重の Month 見解（をとる） in the Calendar and there are date 独房s defined as unselectable by the SpecialDates 支配（する）／統制する, the 使用者 could still select those dates if they were shown as "other month" dates.
• Atlas (at least June 2006 CTP) 干渉するd with the 状況 menus, showing the browsers 状況 menu on 最高の，を越す of PDP's.
• When the MonthYearTextBox is on the page without any DateTextBox or Calendar also there, when xAllowMonthNames is "Show", a javascript error occurred after the 使用者 entered a valid date.
• When the DateTextBox has its popupcalendar 始める，決める with xCallbackOnMonthViewChangeB=true, it did not 解雇する／砲火／射撃 the OnMonthViewChanged event and collect new data from the SpecialDates 支配（する）／統制する.
• When CS_Calendar or MultiSelectionCalendar is 明白な=誤った on a postback, it threw an exception 述べるing a problem with a hidden field.

• In 入ること／参加（者） 見解（をとる）, it may help to start the 名簿（に載せる）／表（にあげる） of answers with a different item to make sure 使用者s aren't just clicking on the first one. 始める，決める the new 所有物／資産／財産 xRandomizeEntriesB to true to start with a 無作為の answer.
• In Results 見解（をとる）, you can now sort the results by the total 投票（する）s, with the highest 投票（する）s at the 最高の，を越す. 始める，決める the new 所有物／資産／財産 xSortAnswersByVotesB to true.

• When the RecentPolls 支配（する）／統制する was 追加するd, design 方式 showed the error "" until you 体制／機構 the <xPolls> 所有物／資産／財産.

• Buttons that 原因（となる） an AJAX callback, like the radcallback callbackButton, can 実証する first by using the PeterBlum.VAM.全世界のs.Page.RegisterCallbackControl.

• When the VAM buttons are used in the Wizard 支配（する）／統制する's 航海 templates and they use the DisableOnSubmit 所有物／資産／財産, a javascript error occurred when the page was submitted.
• When using the {MINIMUM} or {MAXIMUM} 記念品s on a RangeValidator with DataType="二塁打", a value smaller than 0.00009 was 代表するd as a string in 科学の notation.
• The ReadOnlyCondition did not 供給する server 味方する evaluation 正確に on any of these TextBoxes: FilteredTextBox, IntegerTextBox, DecimalTextBox, or CurrencyTextBox.
• ASP.NET 2.0 only: The new ASP.NET 2.0 HiddenField webcontrol was not supported by validators that already supported the older style <input type='hidden' runat='server' /> 支配（する）／統制する.
• When in a 部分的な／不平等な 信用 環境 and you GET the ErrorFormatter 反対する from a Validator's ErrorFormatter 所有物／資産／財産, it threw a SecurityException.
• When using the Visual Studio 2005 built-in web server with Visual Input 安全, the 安全 分析 報告（する）／憶測 threw an InvalidOperationException, "Failed to 地図／計画する the path '/' ".
• Server-味方する memory 漏れる 設立する in the ErrorFormatter 反対する has been 訂正するd.
• Several （弁護士の）依頼人-味方する memory 漏れるs 設立する in Internet Explorer and have been 直す／買収する，八百長をするd.
• When using a MultiConditionValidator with an UnwantedWordsCondition in its 条件s 所有物／資産／財産, the 所有物／資産／財産s Editor threw a Typecast exception.
• When a FilteredTextBox has only these 所有物／資産／財産s 始める，決める to true: Enter and 除外する, it does not 除外する the Enter 重要な.
• ASP.NET 2.0 only: When you call a page with VAM 支配（する）／統制するs from a custom HttpHandler, it threw a NullReferenceException even if you called PeterBlum.VAM.全世界のs.UsingAltHttpHandler.

• 追加するd the CLSCompliantAttribute.

• DateTextBox.xDateBindable, TimeOfDayTextBox.xDateTimeBindable, and CS_Calendar.xSelectedDateBindable needed to 割り当てる a blank date when the BindableMode is TwoWay or SqlType and the DateTime that you pass in is the 最小限 for a SQL date (1/1/1753).
• The stand-alone PopupMonthYearPicker 支配（する）／統制する continued to use the Month and Year value that the 使用者 selected. It needed to 逆戻りする to the 初期の values.
• When the xDateTimeFormatInfo.ShortDatePattern is "d/MM/yyyy" (date separator doesn't 事柄) and DateTextBox.xAllowMonthNames is used, the 自動車 fill of date separators does not work when the 使用者 types a one digit day. For example, "1mar02" does not work while "01mar02" becomes "1-MAR-2002".
• ASP.NET 2.0 議会 only. The DateTextBox.xReadOnlyAllowsPopupCalendarB=true didn't work. (Microsoft has changed the TextBox's class to 保持する the value of the Text 所有物／資産／財産 from the ViewState when ReadOnly is true.)
• When using the Hungarian culture (hu-HU), the (a)自動的な／(n)自動拳銃 tooltip on the DateTextBox showed the date 判型 incorrectly as this text: "D . . ." instead of "D.M.Y".

• VAM has been 実験（する）d with the new EasyListBox v3. Documentation on how to get EasyListBox to work best with VAM is 設立する in the [VAM 製品 folder]\Third Party Support\EasyListBox folder.
• VAM now supports the Q4 2005 解放（する） of Telerik r.a.d. 支配（する）／統制するs, starting at SP2 (RadGrid support starts at SP3). There were some 議会 changes. So as you migrate to this 見解／翻訳／版, please see the 指示／教授／教育s for updated filenames and the <assemblyBinding> tag values. Documentation is 設立する in [VAM 製品 folder]\Third Party Support\Telerik r.a.d. 支配（する）／統制するs folder.
• Support for more 見解／翻訳／版s of Infragistics UltraWebGrid is 含むd. See [VAM 製品 folder]\Third Party Support\Infragistics WebGrid folder.
• Support for Infragistics WebCombo and WebDataInput 支配（する）／統制するs is 含むd. See [VAM 製品 folder]\Third Party Support\Infragistics DataInput and Combo folder.
• The ValidationSummary introduces the method AddMessage(). It 許すs 追加するing messages to the ValidationSummary on the server 味方する, usually in 返答 to errors that are returned by your 商売／仕事 層. See the topic "追加するing ErrorMessages At Runtime" in the "ValidationSummary 支配（する）／統制する" section of the Validation 使用者's Guide.
• The PeterBlum.VAM.全世界のs.Page.RegisterSubmitControl() method now supports the ASP.NET 2.0 LoginStatus 支配（する）／統制する. Just pass the LoginStatus 支配（する）／統制する into the first parameter and an empty string in the second parameter. Now the LoginStatus 支配（する）／統制する will not 原因（となる） （弁護士の）依頼人-味方する validation to occur.
• The Validation 使用者's Guide has a new section covering how VAM can be used with every webcontrol 配達するd in the ASP.NET 枠組み, 含むing all 見解／翻訳／版 2.0 支配（する）／統制するs.
• The PeterBlum.VAM.全世界のs.Page.AddHintToControl() method now supports RadioButtonList, CheckBoxList, and any other 支配（する）／統制する that 器具／実施するs a "GetChildMethod" in custom.VAM.config.
• In ASP.NET 2.0, 支配（する）／統制するs that 服従させる／提出する using __doPostBack will いつかs 実証する and いつかs not, depending on some 事前の validation 活動／戦闘 on the page. Now calls to __doPostBack will never 実証する. If you want validation, use either a VAM 服従させる／提出する 支配（する）／統制する or 生成する the __doPostBack() call using PeterBlum.VAM.全世界のs.Page.GetPostBackEventReference(thecontrol, "", "", 誤った) as 文書d in the Validation 使用者's Guide.

• When the ValueWhenBlank 所有物／資産／財産 on any textbox 含む／封じ込めるs a 選び出す／独身 引用する, it 原因（となる）d a javascript error.
• The DecimalTextBox 報告（する）／憶測d a javascript error when the 使用者 typed a decimal number starting with a decimal separator like ".5".
• When using spinners on numeric TextBoxes and you use a decimal value for the SpinnerIncrement, 一連の会議、交渉／完成するing errors can 原因（となる） strange numbers to appear. This is 予定 to the 80 bit math used by browsers in Javascript. The code now uses a 一連の会議、交渉／完成するing technique to clean up those math errors.
• When using the DropDownListSegment of the MultiSegmentDataEntry 支配（する）／統制する and the 支配（する）／統制する is 始める，決める to 明白な=誤った, later when its 始める，決める to 明白な=true on a postback, the 名簿（に載せる）／表（にあげる）s would be empty instead of 含む／封じ込めるing the items you defined.
• When using the DropDownListSegment of the MultiSegmentDataEntry 支配（する）／統制する and using a validator on the 支配（する）／統制する, the validator didn't 解雇する／砲火／射撃 if you last changed the dropdownlist before moving 焦点（を合わせる） out of the field. (It still 解雇する／砲火／射撃d onsubmit.)
• When using Hints on the MultiSegmentDataEntry 支配（する）／統制する and you 手配中の，お尋ね者 to show validator error messages in the hint, any validator that is 大（公）使館員d to the MSDE did not show its error message. (Validators 割り当てるd to individual segments did show.)
• When using the TabIndex 所有物／資産／財産 on the MultiSegmentDataEntry 支配（する）／統制する, Internet 調査する tabbed first to the 含む／封じ込めるing （期間が）わたる tag before entering the first segment.
• Alignment of segments in the MultiSegmentDataEntry 支配（する）／統制する has been 改善するd. The textboxes were わずかに higher than the dropdownlists. (公式文書，認める that static text between fields remains a little lower, but in line with text in the same line outside of the 支配（する）／統制する.)
• IgnoreConditionValidator would not show its error message in the ValidationSummary when the ValidationSummary was an earlier 支配（する）／統制する in the page.
• In ASP.NET 2.0 only: When using the validation group 指名する that starts with the + 記念品, （弁護士の）依頼人-味方する validation did not 妨げる submitting the page when there are 無効の validators in some 事例／患者s.
• When using the OverrideClientSideEvaluation 所有物／資産／財産 on a validator along with the PeterBlum.VAM.全世界のs.Page.ControlErrorCssClass 所有物／資産／財産, when an error was 体制／機構 to show the error CssClass, it did not 回復する to the 初めの class after an edit to the textbox.
• When a LinkButton is used with a 確認する message, either on 全世界のs.Page.ConfirmMessage or on LinkButton.AltConfirmMessage, the 確認する message appeared twice if the page was valid and the 使用者 selected "承認する".
• In the ASP.NET 2.0 GridView 支配（する）／統制する, the paging links would 妨げる 地位，任命する 支援する if there was an 無効の 支配（する）／統制する inside the grid that was already showing its error message.
• In the ASP.NET 2.0 議会 only: When using the GridView 支配（する）／統制する with VAM's CommandField, the Save/Update button did not always 解雇する／砲火／射撃 the RowUpdated event.
• In the ASP.NET 2.0 議会 only: When you use the StyleSheetTheme 所有物／資産／財産 on the Page, its values would not be 反映するd in design 方式 of VAM's 支配（する）／統制するs.
• In the ASP.NET 2.0 議会 only: You are supposed to be able to turn off the default style sheet <link> tag by setting the VAM_StyleSheetFileUrl 重要な in the web.config とじ込み／提出する to an empty string. It didn't work. The default style sheet URL was 供給（する）d instead.
• In the ASP.NET 2.0 議会 only: When 試みる／企てるing to 追加する the <link> tag to the style sheet とじ込み／提出する, if your <長，率いる> tag 含む／封じ込めるs the symbols <% and %>, an HttpException was thrown. Now it will omit the link tag. If you use <@Page trace="true" >, the trace will 知らせる you when this happens.
• When you called the javascript 機能（する）／行事 VAM_RunAllFSC(), it did not run any MultiFieldStateControllers or MultiFSCOnCommand 支配（する）／統制するs.
• The method PeterBlum.VAM.全世界のs.UsingAltHttpHandler() did nothing when Page.IsPostBack is true. It should work 関わりなく IsPostBack.
• When VAM is used with Peter's Date 一括, オペラ 7 and 8 failed to popup the calendar and help menu reliably. いつかs they would not popup at all.
• In ASP.NET 2.0 only: When you 体制／機構 the Form with the DefaultButton 所有物／資産／財産, use the ENTER 重要な to 服従させる／提出する when there is a validation error. It will 報告（する）／憶測 the error. 直す／買収する，八百長をする the error and use ENTER again. That page will 服従させる／提出する except it won't 解雇する／砲火／射撃 the 訂正する 地位，任命する 支援する event handler for the default button. This has been 訂正するd.
• In ASP.NET 2.0 only: When using IIS to 地図／計画する a 事実上の URL to a physical path, if your mapping does not end in a 追跡するing \ character, design 方式 will 報告（する）／憶測 errors in 位置を示すing your licenses and custom.vam.config とじ込み／提出する.
• In ASP.NET 2.0 議会 only: いつかs validators showed this message in design 方式: "No とじ込み／提出する is 設立する at VAM\VAM.config. This とじ込み／提出する is 要求するd to run VAM.". Notice the とじ込み／提出する path is 正確に／まさに "VAM\VAM.config". Only this 事例／患者 was a bug that is now 直す／買収する，八百長をするd. You should 推定する／予想する this error with other paths to 示す a 体制／機構 problem.
• When you have a VAM 控訴 開発.lic とじ込み／提出する （軍隊を）展開する，配備するd to 生産／産物 and its used, it should 報告（する）／憶測 an error 述べるing a 限界 of IP 演説（する）／住所s. Instead, it 供給するd the wrong message, which was: "There are no valid [modulename] licenses とじ込み／提出するs 設立する in [filepath]".
• VAM 3.0.2 and 3.0.3 only: In IE Mac 5.0 and 5.1, validation would fail when submitting the page.
• In the PageSecurityValidator, if you 始める，決める DetectInjectionSymbolsInQueryString=true but did not have any 支配するs in CookieRules or QueryStringRules, the DetectInjectionSymbolsInQueryString feature was ignored.
• When a MultiSegmentDataEntry 支配（する）／統制する 含む／封じ込めるd DropDownLists and was 明白な=誤った, any value 割り当てるd to it would not be 保存するd in the viewstate at postback.

• In ASP.NET 2.0 only: The "Bindable" 所有物／資産／財産s introduced in v1.1.10 now support intellisense. 思い出の品: they can only be 割り当てるd with DataBinding notation in the HTML 鮮明度／定義 of the 支配（する）／統制する.
• The "Bindable" 所有物／資産／財産s now support setting their value using strings. (You cannot GET as a string.)

• In FireFox, Mozilla, and Netscape 7+, when using 国境s around 独房s in the calendar and there is no cellspacing, the 国境 lines looked strange.
• If you type into any of the textboxes or even 攻撃する，衝突する tab to move through them 事前の to the page 存在 initialized, you will get a javascript error. Now it will give you an 警報 box to 知らせる the 使用者 to 延期する their 入ること／参加（者）.
• On Mozilla based browsers, if any of the textboxes are ReadOnly and you tab to them, tab stops working. You have to use the mouse to move 焦点（を合わせる） to another field.
• いつかs a 二塁打-click on the calendar toggle button would leave the calendar stuck open.
• Only in v1.1.10: When any of the textboxes where placed into a TableCell 支配（する）／統制する, design 方式 would not show the （米）棚上げする／（英）提議する in its normal 判型. Instead it would appear as "[（米）棚上げする／（英）提議する TableID]".
• Only in v1.1.10: When any of the textboxes are 追加するd into 確かな 支配（する）／統制するs, design 方式 will show them as an error. The error message is "反対する 言及／関連 not 始める，決める to an instance of an 反対する."
• In the ASP.NET 2.0 議会 only: When 試みる／企てるing to 追加する the <link> tag to the style sheet とじ込み／提出する, if your <長，率いる> tag 含む／封じ込めるs the symbols <% and %>, an HttpException was thrown. Now it will omit the link tag. If you use <@Page trace="true" >, the trace will 知らせる you when this happens.
• Only in v1.1.10: the TimeTextBoxCompareValidator 生成するd a javascript error when its TimeOfDayTextBox was not 大（公）使館員d to a DateTextBox.
• QuickDateMenu ignored settings of the に引き続いて 所有物／資産／財産s and used their default values: xOnPopup, xOnPopDown, xHorzPosition, xHorzPositionOffset, xVertPosition, xVertPositionOffset, and xIEFixPopupOverList.
• When using the VAM Style Validators to 評価する a DateTextBox, cultures that use a space character for their date separator would fail to 実証する.
• In the ASP.NET 2.0 議会 only: All of the validators would 生成する a javascript error when their EnableClientScript 所有物／資産／財産 was 誤った.
• When any popup 支配（する）／統制する appears within a scrolling element of a page, if that element was scrolled more than the 高さ of the page, the popup appeared too high on the page.

• ASP.NET 2.0 議会 含むd. 供給するs support of ASP.NET 2.0 features 含むing XHTML, easier localization on strings, (a)自動的な／(n)自動拳銃 体制／機構 of the style sheet <link> tag, 除去 of obsolete API features and more. See the 使用者's Guide for the section "ASP.NET 2.0 and Visual Studio.逮捕する 2005 Enhancements".
• Documentation has been 高めるd using techniques 以前 適用するd to the VAM 3 昇格. There is a separate 取り付け・設備 Guide, richer step-by-step 指示／教授／教育s for 追加するing 支配（する）／統制するs, 延長するd 詳細（に述べる）s on many topics where there was heavier 負担 on tech support, and quick jump （米）棚上げする／（英）提議するs on many sections.
• ASP.NET 2.0 議会 only: When you use the SpecialDates 支配（する）／統制する with CS_Calendar, you can now have it use callbacks (AJAX 科学（工学）技術) to update the SpecialDates 支配（する）／統制する with new data for each month. This 減ずるs the size of the data passed to the browser by 限界ing the data to just one month each time. See the xCallbackOnMonthViewChangeB 所有物／資産／財産.
• 広範囲にわたる enhancements to the CS_Calendar.OnMonthViewChanged event. The MonthViewChangedArgs parameter 供給するs start and end dates for the month shown 加える 接近 to the CS_Calendar and its SpecialDates 支配（する）／統制する.
• When using the CS_Calendar.OnMonthChangedEvent, it 普通は only 解雇する／砲火／射撃s during a 地位，任命する 支援する 原因（となる）d by changing the month (it depends on the xAutoPostBackOnMonthViewChangeB 所有物／資産／財産). Often 使用者s 体制／機構 the OnMonthChangedEvent to 居住させる the SpecialDates 支配（する）／統制する and want it to be called each time the page is created, not just on a month change 地位，任命する 支援する. Use the new xAlwaysInvokeOnMonthViewChangedEventB 所有物／資産／財産.
• CS_Calendar 供給するs a new 所有物／資産／財産, xCurrentMonthViewed. It is a DateTime 反対する 代表するing the first day of the 現在の month 見解（をとる）d.
• DateTextBox, MonthYearTextBox, and AnniversaryTextBox 申し込む／申し出 a new 所有物／資産／財産, xAdditionalDateSeparators. いつかs you want to 許す the 使用者 to type other date separators than then one 供給（する）d by xDateTimeFormatInfo.DateSeparator. Define those other date separators in this 所有物／資産／財産.
• DateTextBox, MonthYearTextBox, and AnniversaryTextBox 申し込む／申し出 a new 所有物／資産／財産, xMonthNamesUppercaseB. When you use xAllowMonthNames=Show, the month 指名するs are reformated into uppercase. With xMonthNamesUppercaseB 始める，決める to 誤った, the month 指名するs can now be the same 事例／患者 they are defined in the xDateTimeFormatInfo 所有物／資産／財産.
• TimeOfDayTextBox and DurationTextBox have a new 所有物／資産／財産 xDecimalMode which lets you 決定する the 役割 a period character has in time 入ること／参加（者）. 事前の to this, the period was always used to 代表する a decimal form of time. Now it can be 無能にするd or used as an 代案／選択肢 time separator with this 所有物／資産／財産.
• TimeOfDayTextBox and DurationTextBox have a new 所有物／資産／財産, xBlankStartsAt. It 決定するs the 初期の value 割り当てるd to a blank textbox when using spinners. It can be the 現在の time, min/max time, or a value from xBlankStartsAtValue.
• There are new ways to get and 始める，決める values on the data 入ること／参加（者） 支配（する）／統制するs when binding. See the DateTextBox.xDateBindable, CS_Calendar.xSelectedDateBindable, and TimeOfDayTextBox.xDateTimeBindable 所有物／資産／財産s.
• When using SmartNavigation or IFrames, いつかs popups appear transparent or have other strange 製図／抽選 problems. This is 予定 to a 切り開く／タクシー／不正アクセス to 許す popups to appear over listboxes and dropdownlists in IE/勝利，勝つ 5.5-6.x. One way to 解決する this problem is to turn off the 切り開く／タクシー／不正アクセス. That can now be done with the new 所有物／資産／財産 xIEFixPopupOverList 所有物／資産／財産, 設立する on the さまざまな popup 支配（する）／統制するs.
• DateTextBox no longer 包むs its buttons under the textbox when squeezed for space. It 供給するs an HTML コンテナ to 妨げる wrapping. This コンテナ is controlled by the xContainerMode 所有物／資産／財産. It can be turned off. xContainerMode 取って代わるs the xAutoAbsPositionModeB 所有物／資産／財産.
• TimeOfDayTextBox and DurationTextBox no longer use 絶対の positioning for its spinner buttons. It no longer 包むs its help button under the textbox when squeezed for space. It 供給するs an HTML コンテナ to keep all 支配（する）／統制するs in one 列／漕ぐ／騒動. This コンテナ is controlled by the xContainerMode 所有物／資産／財産. It can be turned off. xContainerMode 取って代わるs the xAutoAbsPositionModeB 所有物／資産／財産.
• You can now 任命する／導入する the PetersDatePackage folder under the [web 使用／適用 root folder] without setting any 重要なs up in the web.config とじ込み／提出する. This is the preferred 場所 for ASP.NET 2.0.
• The TrueBrowser class now supports an event handler, TrueBrowser.Customize, where you can configure a TrueBrowser 反対する yourself based on the UserAgent 供給（する）d. This 許すs easier 支配（する）／統制する over browser configurations. See the section "Customizing a TrueBrowser 反対する" in the 使用者's Guide.
• Design 方式 now shows the spinner buttons on TimeOfDayTextBox and DurationTextBox.
• 状況 menus now 申し込む／申し出 several positioning 所有物／資産／財産s: xHorizPosition, xVertPosition, xHorizPositionOffset, and xVertPositionOffset.
• The xOnChangeFunctionName 所有物／資産／財産 on DateTextBox and TimeOfDayTextBox now supports a way to be called even when the textbox is blank or has erroneous data. Use the xOnChangeFunctionAlwaysB 所有物／資産／財産 and 追加する the new pError parameter to your 機能（する）／行事.
• To support XHTML compatibility, all <img> tags now 供給する a value for their alt= せいにする. In many 事例／患者s, you can 始める，決める the value.
• Better 扱うing of Mono by 避けるing changing the 事例／患者 of とじ込み／提出する paths and supporting the Unix directory separator character.
• When 割り当てるing TimeOfDayTextBox.xDateTime to DateTime.MinValue or calling SetEmpty(), it now （疑いを）晴らすs the DateTextBox 同様に as the TimeOfDayTextBox.
• Support of the IndexOf() method on the SpecialDates.xDates collection.

• オペラ 7 and 8 would not popup the Help button menu.
• オペラ 8 would often misposition the popups to be 紅潮／摘発する with the 最高の，を越す of the page.
• Some cultures 明示する a 追跡するing date separator (含むing Hungarian (hu) and Latvian (lv)). These would 生成する both （弁護士の）依頼人 味方する and server 味方する errors.
• When using decimal 入ること／参加（者） in TimeOfDayTextBox or DurationTextBox, if the 使用者 typed "08" or "09" for hours, it would 変える the time into 12:59:59.
• Better positioning of popups when they have a wide 国境 or they are 含む／封じ込めるd in another element that has a wide 国境.

• With the new xEntryAnswerElements 所有物／資産／財産, you can 判型 the 無線で通信する button answers with values 代表するing the 現在の total for the answers 含むing 妨げる／法廷，弁護士業 graphs, total 投票（する）s, and 百分率.
• With the new xRotatingPolls 所有物／資産／財産, you can make new 投票s appear すぐに after the 使用者 投票（する）s on the 現在の 投票. See the "回転／交替ing 投票s 方式" section of the 使用者's Guide.
• With the new xThrowExceptions 所有物／資産／財産 始める，決める to 誤った, if your database throws an exception, it will no longer be sent 支援する to the page. Instead, the PollControl will show itself in the "There are no 投票s to show" 見解（をとる）.

• In design 方式, when showing both the 名簿（に載せる）／表（にあげる） and 投票 section on the 最近の 投票s 支配（する）／統制する (経由で a 権利 click on the 最近の 投票s 支配（する）／統制する), the xPolls.ToolTip 所有物／資産／財産 gets 始める，決める to say "DEMO MODE".
• ASP.NET 2.0/Visual Studio.逮捕する 2005 使用者s could not get 投票s to save 投票（する）s when used inside a UserControl, content form of a MasterPage, or any 指名するing コンテナ.
• いつかs when a 妨げる／法廷，弁護士業 反映するd a value below 0.01, the 妨げる／法廷，弁護士業 would be too large for the value.

• The PeterBlum.VAM.全世界のs.Page.RegisterKeyClicksControl() method now supports mapping the 機能（する）／行事 重要なs to buttons. Use values of 112-123 to 代表する these 重要なs. 公式文書，認める that not all browsers support 迎撃するing 機能（する）／行事 keystrokes but IE, Mozilla, FireFox, and Netscape 7+ do.
• The FieldStateController now 申し込む／申し出s the 所有物／資産／財産 SupportClientSideLookupByID which was 以前 only on validators. With it, you can 体制／機構 javascript to invoke the FSC, 修正する its （弁護士の）依頼人-味方する 所有物／資産／財産s and get the value returned from 評価するing the 条件.
• Diner's Club changed their credit card numbers. The vam.config とじ込み／提出する 含む／封じ込めるs the updated numbering system.
• The CharacterValidator and CharacterCondition have a new 所有物／資産／財産, 除外する. When true, the character 始める，決める defined is 除外するd; all other characters are permitted. The NotCondition 所有物／資産／財産 has been depreciated on these classes because it doesn't 始める，決める up the 訂正する logic for 除外.
• Better alignment and positioning of MultiSegmentDataEntry's 独房s within that 支配（する）／統制する, 特に on オペラ 7+ and Safari.
• Continued 改良s on 陳列する，発揮するing the spinners of numeric textboxes without 絶対の positioning, に引き続いて up from the 初期の changes in v3.0.2. These 支配（する）／統制するs now can 避ける wrapping the spinners の上に the next line on several browsers, using enclosing （期間が）わたる or （米）棚上げする／（英）提議する tags.
• MultiSegmentDataEntry 支配（する）／統制する uses the white-space:nowrap style to 妨げる it from wrapping individual segments to the next line when squeezed for space.
• v3.0.2 introduced an undocumented 所有物／資産／財産 called AutoAbsPositionMode on numeric textboxes. This has been depreciated. Use the new AutoContainer 所有物／資産／財産 instead.
• In design 方式, when a validator has ErrorFormatter.陳列する，発揮する=非，不，無, it now 適用するs the styles of the ErrorFormatter.
• 輸入する VAM Classes.exe and 変える Page to VAM.exe 使用／適用s now （悪事，秘密などを）発見する read only とじ込み／提出するs and 妨げる overwriting them. This helps when you keep とじ込み／提出するs in a Source 支配（する）／統制する 環境.

• FilteredTextBox with no filtering 所有物／資産／財産s 体制／機構 許すs all characters. That's 罰金. However, when you have a CharacterValidator 大（公）使館員d, you got a javascript error as the validator 評価するs, 予定 to a bad 正規の／正選手 表現.
• When using any validator whose DataType is 始める，決める to Date and the 使用者 enters 3 or more 削除するs, you would get a javascript error.
• When using the CalculationController with a ConditionCalcItem 割り当てるd to a 条件 反対する of type MultiCondition or CountTrueConditions, a NullReferenceException may occur.
• Some older browsers will 報告（する）／憶測 a javascript error when using any of the VAM TextBoxes. 含むs オペラ 6 and Netscape 4.
• Some older browsers continued to 生成する javascript that 始める，決めるs up the 自動車 （犯罪，病気などの）発見 of javascript, when the browser didn't support that code. The browser may 報告（する）／憶測 javascript errors.
• The CharacterValidator/条件 automatically uses character 始める，決める 所有物／資産／財産s on the FilteredTextBox, when 大（公）使館員d. If the CharacterValidator did not have at least one of its own character 始める，決める 所有物／資産／財産s enabled, you would get an exception.
• In the ASP.NET 2.0 議会s from v3.0.2, 絶対 positioned validators would appear without their 絶対の positioning in design 方式 of VS.NET 2005. You couldn't even use the Layout; Position; 絶対の menu 命令（する） to work around this. There was no problem at runtime.
• In the ASP.NET 2.0 議会s from v3.0.2, when using the 開発 Server that is built into Visual Studio 2005, design 方式 would not show any of the default images so long as their URL starts with "~/".

• Support for ASP.NET 2.0 features. 議会s 収集するd with ASP.NET 2.0 Beta 2 are 含むd and 供給する 広範囲にわたる enhancements 関係のある to the new features 申し込む／申し出d in ASP.NET 2.0. Each 使用者's guide has a section 詳細（に述べる）ing what has changed. The 取り付け・設備 Guide has steps to update from an ASP.NET 1.x 場所／位置 to 2.0. WARNING: This ソフトウェア is 収集するd with ASP.NET 2.0 Beta 2. It will be recompiled with the 解放（する） 候補者 builds when they become 利用できる. A Beta 2 議会 may break when run on a 場所／位置 using the 解放（する） 候補者. A 解放（する） 候補者 議会 may break when run on a 場所／位置 using Beta 2. So try to use 見解／翻訳／版s of ASP.NET 2.0 that are the same 解放（する） as these 議会s.
• （弁護士の）依頼人-味方する validation support for the Telerik r.a.d. 支配（する）／統制するs 控訴 含むing r.a.d. editor, r.a.d. grid, r.a.d. combobox, r.a.d. menu, and r.a.d. tabstrip. See the documentation in the Telerik r.a.d. 支配（する）／統制するs folder to 始める，決める up this support.
• Several features that support images now let you 割り当てる the 代案／選択肢 text (the <img alt=''> せいにする) so that when the browser fails to 負担 the image, some text is 陳列する，発揮するd:
  • AlertImageErrorFormatter and TooltipImageErrorFormatter now have the ImageAltText 所有物／資産／財産. It uses a 全世界の value from PeterBlum.VAM.全世界のs.Page.DefaultImageErrorFormatterImageAltText or the 全世界の Settings Editor by default.
  • The images of RequiredFieldMarker and RequiredFieldDescription now use the 全世界の value from PeterBlum.VAM.全世界のs.Page.DefaultRequiredFieldImageAltText or the 全世界の Settings Editor.
  • The NoErrorFormatter uses the 全世界の value from PeterBlum.VAM.全世界のs.Page.DefaultNoErrorFormatterImageAltText or the 全世界の Settings Editor.
  • The spinners on numeric textboxes will show "+1" and "-1" or whatever value you define for incrementing.
• The spinners on numeric textboxes no longer use 絶対の positioning, which was 原因（となる）ing 使用者s to call VAM_MoveSpinners. It now uses a （米）棚上げする／（英）提議する that has style=陳列する，発揮する:inline;. It should now 正確に position without you calling VAM_MoveSpinners. However, still use VAM_MoveSpinners if you show or hide the textbox to show and hide the spinners. SIDE EFFECT: 絶対の positioning always positioned the spinners to the 権利, even when there wasn't any 審査する space. inline positioning will 包む the spinners below if they don't fit on the 審査する. 権利 to left text will also position the spinners to the left now.
• The CombinedErrorMessages 支配（する）／統制する has a new 所有物／資産／財産, ShowFirstMsgOnly. While the CombinedErrorMessages 支配（する）／統制する is designed to show several validators error messages 同時に, some developers believe its easier for their 使用者s to see just one error message at a time. When you 始める，決める this 所有物／資産／財産 to true, only the first Validator that is 無効の will show its error message. As that one is 直す／買収する，八百長をするd, the CombinedErrorMessages 支配（する）／統制する will show the next Validator that is 無効の.
• The CalculationController.DecimalPlaces 所有物／資産／財産 used to 申し込む／申し出 1-4 decimal places. Now it 申し込む／申し出s 1-10 decimal places.
• The CalculationController 申し込む／申し出s the ExtraControlsToRunThisAction 所有物／資産／財産 (like most of the other 支配（する）／統制するs) so you can have other 支配（する）／統制するs 解雇する／砲火／射撃 the 計算／見積り.
• PeterBlum.VAM.TrueBrowser.Customize is a new 委任する／代表 that is called when a new UserAgent is （悪事，秘密などを）発見するd. It lets you customize the 所有物／資産／財産s of the TrueBrowser 反対する for that UserAgent. This way, you can introduce support for new browsers more easily.
• The <ThirdPartyControls> section now can define a 機能（する）／行事 that 扱うs the 外見 when there is an error. It is the <SetErrorStyleScript> tag.
• The （犯罪，病気などの）発見 of javascript feature was only 体制／機構 if you had at least one validator on the page. Now it is 体制／機構 if you have at least one VAM 支配（する）／統制する with （弁護士の）依頼人-味方する support, such as a VAM TextBox or FieldStateController.
• A page with several CalculationControllers and FieldStateControllers could have poor 業績／成果 as it initializes. The 速度(を上げる） has been 劇的な 改善するd.
• The web.config とじ込み／提出する 重要な "VAM_ScriptVirtualPath" now 許すs the 記念品 "{VERSION}". It 取って代わるs the 記念品 with the same 指名する of the folder 含む／封じ込めるing the scripts as you find in the 製品 取り付け・設備. This way, you can have 多重の 見解／翻訳／版s of VAM scripts 任命する／導入するd without updating the VAM_ScriptVirtualPath 重要な.

• When you have a module license (not the 控訴 license), you are 許すd to use the CustomValidator. If you the only VAM 支配（する）／統制する you use on a form is the CustomValidator, it gave a license error. So long as you had one valid license 体制／機構, the error should not have occurred.
• Using a DataTypeCheckValidator for DataType=Date will not 報告（する）／憶測 an error when the year entered is 5 or more digits on the （弁護士の）依頼人-味方する but would 報告（する）／憶測 an error on the server 味方する. It now 報告（する）／憶測s an error with 5 or more digit years in both 事例／患者s.
• When the DuplicateEntryCondition is used under a MultiConditionValidator or CountTrueConditionValidator, a NullReferenceException occurred.
• When DecimalTextBox uses a number in ValueWhenBlank and TrailZeroDecimalPlaces=0, the spinners did not work so long as the textbox matches ValueWhenBlank.
• IE for Windows 5.0 would 報告（する）／憶測 a javascript error when 試みる／企てるing to show an 警報 with an error message. This is 予定 to a bug in the browser's 正規の／正選手 表現 parser that does not 受託する an 表現 designed to find an HTML tag in the error message so those tags can be stripped out. This 直す／買収する，八百長をする leaves the HTML tags in place when the 警報 is shown on the IE/勝利，勝つ 5.0 browser.
• CalculationController 生成するd a javascript error when using the ConstantCalcItem 反対する with a CultureInfo whose NumericDecimalSeparator is not a period character.
• CalculationController 生成するd a runtime exception "The Owner 所有物／資産／財産 has not been 割り当てるd to a 支配（する）／統制する which 設立するs a NamingContainer used to find other 支配（する）／統制するs." when you 追加するd a CalcItem 反対する programmatically in 確かな 事例／患者s.
• CalculationController did not 追加する the ".0" to a decimal value 陳列する，発揮するd in a label when that value is a whole number. This was only a server 味方する problem, based on using the AutoShowValue 所有物／資産／財産. So a value of 2.0 would appear as "2" when it should appear as "2.0".
• CalculationController using a ConditionCalcItem whose ExpressionFalse 所有物／資産／財産 is empty will 原因（となる） a javascript error.
• When using Interactive Hints to show validation errors in the hint, if a MultiConditionValidator 供給（する）d an error, there would be 多重の copies of the same error message shown in the hint.
• Intrasoft WebCombo 3.0 干渉するd with （弁護士の）依頼人-味方する validation when submitting. If there was a validation error, the page would still 服従させる／提出する. A code change to VAM 許すs WebCombo's scripts to notice that VAM has requested the page not to be submitted.
• If you 始める，決める a LinkButton to Enabled=誤った, some of the （弁護士の）依頼人-味方する code still runs. 特に, validation and 無能にするing buttons for 服従させる／提出する (DisableOnSubmit 所有物／資産／財産). This is because IE does not 現実に stop the code from running on a 無能にするd linkbutton. Mozilla doesn't even support the Enabled=誤った setting, leaving the linkbutton looking enabled and running the validation/無能にする code but not submitting the page. 防御の code has been 追加するd to 避ける 実証するing and 無能にするing on 服従させる／提出する when you click on a 無能にするd LinkButton either on IE and Mozilla.
• Using the VAM Button or LinkButton with DisableOnSubmit=true and CausesValidation=誤った, a click on the Button did not 無能にする itself or any of the other 無能にするd 支配（する）／統制するs.
• When using PeterBlum.VAM.全世界のs.Page.TextHiliteFieldsCssClass and the validator has EnabledClientScript=誤った, if the TextBox 存在 実証するd has CssClass="", the fields that are 影響する／感情d by TextHiliteFieldsCssClass will get stuck in their "error" style after the error is 直す／買収する，八百長をするd.

• When the Group 所有物／資産／財産 uses the special symbol "+", it did not work with （弁護士の）依頼人 味方する validation. There was a 判型 change of the value of any 支配（する）／統制する's UniqueID 所有物／資産／財産 that broke a 正規の／正選手 表現 存在 used to 評価する the group 所有物／資産／財産.
• When using the CalculationController and you programmatically 追加する a NumericTextBoxCalcItem to the 表現s 所有物／資産／財産 with its TextBoxID 所有物／資産／財産 割り当てるd, it would throw a NullReferenceException.
• Textboxes that have TabOnEnterKey=true did not tab on the enter 重要な 圧力（をかける） when MaxLength is 0.

• PeterBlum.VAM.安全.全世界のs.CleanupInputKeepingTags and CleanupInputKeepingTags2 will clean up another Script 注射 attack pattern, 取って代わるing it with "!!".

• When the 開会／開廷／会期 is 無能にするd (web.config <sessionState> 方式 is Off or <@Page enableSessionState=誤った >), an exception would occur 示すing the 開会／開廷／会期 is 無能にするd.
• When the sessionState is "StateServer", a TypeCastException いつかs occurred.
• When any of VAM's textboxes are 体制／機構 with to use the TabOnMaxLength, 急速な／放蕩な typing would 減少（する） keystrokes.
• CurrencyTextBox permitted typing the parentheses characters when AllowNegatives 所有物／資産／財産 is 誤った. It would not consider this valid. So the DataTypeCheckValidator would still stop the 入ること／参加（者） from 存在 submitted.
• During server 味方する validation, the MultiSegmentDataEntryValidator did not 報告（する）／憶測 an error when IgnoreBlankText is 誤った and the 使用者 left the field blank. It worked 適切に on （弁護士の）依頼人-味方する validation.
• The MultiSegmentDataEntry 支配（する）／統制する would 生成する a javascript error if all segments are DropDownListSegments.
• When the MultiSegmentDataEntry 支配（する）／統制する has a DropDownListSegment and a MultiSegmentDataEntryValidator, （弁護士の）依頼人-味方する validation failed with a javascript error.
• When using the MSStyle validators, design 方式 報告（する）／憶測d an error message instead of 製図／抽選 the actual validator. The message was "反対する 言及／関連 not 始める，決める to an instance of the 反対する".
• When using the MSStyle CustomValidator and you had text between the start and end tags with a NEWLINE character, you would get a javascript error at runtime.
• The 所有物／資産／財産 Editor window for the ErrorFormatter 所有物／資産／財産 (on a validator) would 生成する an error message when you saved a template. It would save 首尾よく. The 所有物／資産／財産 Editor window for the 表現 所有物／資産／財産 on the RegexValidator would do the same when you saved an 表現.
• PeterBlum.VAM.全世界のs.Page.RegisterKeyClickControl() and the EnterSubmitControlID 所有物／資産／財産 did not work on Mozilla-based browsers. They 生成するd a javascript error.
• CalculationController 生成するd a javascript error on Mozilla-based browsers instead of showing validator errors associated with the 計算／見積り.

• CombinedErrorMessages 支配（する）／統制する would 報告（する）／憶測 an error about an incorrect ErrorFormatter 所有物／資産／財産. VS.NET 2005 design 方式 追加するd a 所有物／資産／財産 指名する "ErrorFormatter" to the 支配（する）／統制する which previous 見解／翻訳／版s did not, and therefore had no 防御の coding to 避ける the error. That 防御の coding is now in place. Alternatively, you can 削除する the 所有物／資産／財産 指名するd "ErrorFormatter" in the ASP.NET text tag for this 支配（する）／統制する.

• Safari has 厳しい bugs with its Date 反対する when using "UTC" (全世界の／万国共通の Time). (This only 影響する／感情s 見解／翻訳／版s 1.0 - 1.2.x; 1.3 seems to work 正確に.) It returns the wrong date, often off by 1 month, when the Mac's Time Zone is at Greenwich Mean Time (GMT) and 予定 west and Daylight 貯金 Time 適用するs to the date. There is no way to 避ける this bug. However, the javascript code has been 修正するd to 限界 the 衝撃 so that it is off by one day. When you see dates on the calendar, it will look 承認する. When you select a date, it will be the 訂正する date. However, as you popup the calendar or change the month, the selected date will visually jump 支援する one day. Still it will use the 訂正する date.
• Safari has incorrectly defined the 限界s of the Javascript date 反対する as Dec 14, 1901 - Jan 1, 2038. The 訂正する 範囲 easily 越えるs Jan 1, 0001 - Dec 31, 9999 on all other browsers and as defined in the javascript spec.
  As a result, all （弁護士の）依頼人 味方する features that 許す a larger 範囲 will be 欠陥のある outside this 範囲 on Safari. SpecialDates were more 逆に 影響する／感情d by this problem in that if you leave a SpecialDateRange, SpecialDayOfWeek, or SpecialAnnualDate 反対する's xEndDate unassigned (so that it goes to 9999), the （弁護士の）依頼人-味方する ignores these 反対するs. This has been 直す／買収する，八百長をするd by internally 課すing a 限界 of 12/31/2037.
• When using the MonthYearTextBox or MonthYearPicker and only one of these 所有物／資産／財産s is 割り当てるd - xMinDate or xMaxDate, the months outside the date 範囲 did not 薄暗い 正確に.
• When DateTextBox or MonthYearTextBox are using xAllowMonthNames and the culture 割り当てるd to xDateTimeFormatInfo is a different language than the culture of the page, the 初期の date shown had the month 指名する using the language of the page, not of xDateTimeFormatInfo.
• When Telerik RadEditor is on the page with a Peter's Date 一括 支配（する）／統制する, their 状況 menu also 明らかにする／漏らすd the 基準 IE 状況 menu. The IE 状況 menu should have been hidden.
• When using VAM Validators that change the background color of these textboxes on error, just tabbing through either DateTextBox or TimeOfDayTextBox 誘発する／引き起こすd a RequiredTextValidator 割り当てるd to them on any Mozilla-based browser.
• ICE Browser 5.05 原因（となる）d an exception to be raised.
• Some !DOCTYPE settings will 原因（となる） the popup calendar to popup in the wrong 場所 on IE, 特に if they are 近づく the 底（に届く） of the page as the code designed to 転換 the calendar when it goes outside the 明白な 地域 is 伴う／関わるd.

• In Safari, the さまざまな VAM textboxes filtered out the arrow 重要なs, home, end, pageup and pagedown.
• When using 多重の validation groups and 多重の ValidationSummary 支配（する）／統制するs that have AutoUpdate=true, once a ValidationSummary was shown and you edited a field, it 含むd all validators on the page instead of those in its own group.
• Introduced in v2.0.2, when you had a CustomValidator that 含むd （弁護士の）依頼人-味方する code, had nothing 割り当てるd to ControlIDToEvaluate/ControlToEvaluate, and the page is using 全世界のs.Page.ShowAlertOnSubmit, the 警報 appeared showing the error of your validator even when its valid. If the page was 完全に valid, the 警報 appeared and when the 使用者 clicks 承認する, the page 地位，任命するd 支援する.
• When 全世界のs.Page.FocusOnChange is true and you are using a CompareTwoFieldsValidator and your textboxes are IntegerTextBox, DecimalTextBox or CurrencyTextBox, if you entered a value into the second textbox that will 誘発する／引き起こす the validator then click 直接／まっすぐに into the first textbox, 焦点（を合わせる） would 速く jump between the two textboxes. It would not stop.
• When using the 全世界のs.Page.ControlErrorCssClass 所有物／資産／財産 with a validator that has a "cannot 評価する" 明言する／公表する, if you 原因（となる）d that validator to show an error then edited the textbox to match the "cannot 評価する" 明言する／公表する, the ControlErrorCssClass style would remain even though the validator error message was 除去するd. ありふれた "cannot 評価する" 明言する／公表するs are validators with a DataType 所有物／資産／財産 when the textbox that they are 評価するing is empty.
• When using the 全世界のs.Page.ControlErrorCssClass 所有物／資産／財産 with an IntegerTextBox, DecimalTextBox or CurrencyTextBox, several validators that point to 多重の textboxes could 始める，決める the ControlErrorCssClass style sheet without showing a validation error. This is an unusual 事例／患者.
• 変える Pages To VAM.exe 公共事業（料金）／有用性 would 報告（する）／憶測 an error: "索引 was outside the bounds of the array" when the filename of the code behind 声明 含む／封じ込めるd a minus or space character.
• When using the CustomValidator from the PeterBlum.VAM.MSStyle 議会 (<m2v:CustomValidator>) and its ControlToValidate 所有物／資産／財産 is unassigned, the ValidationSummary 支配（する）／統制する did not show the error message on a （弁護士の）依頼人-味方する update. This 状況／情勢 要求するd the CustomValidator to have a （弁護士の）依頼人-味方する validation 機能（する）／行事.
• When using the Internet Explorer TabStrip WebControl with a validator on a page and the PeterBlum.VAM.全世界のs.Page.FocusOnChange 所有物／資産／財産 is true, if the first 活動／戦闘 after editing a field is to click on a tab, it would not 始める，決める 焦点（を合わせる） to the field with the error. If javascript errors are shown, one will appear: "Cannot 始める，決める 焦点（を合わせる）".
• When a \ character is in the ErrorMessage or SummaryErrorMessage 所有物／資産／財産s, it and the character that follows is not shown when （弁護士の）依頼人-味方する validation 陳列する，発揮するs the message.
• Since the devedge.netscape.com 場所／位置 の近くにd, the 正規の／正選手 表現 所有物／資産／財産 Editor page had a bad link when you clicked on the "Regex Character Chart" button. The same page is at http://synchro.逮捕する/docs/js/ref/regexp.html. The button now points to it.
• ICE Browser 5.05 原因（となる）d an exception to be raised.
• When using Peter's Date 一括 with the VAM-拡張s, VAM's RangeValidator is supposed to automatically retrieve values for 最小限 and 最大限 所有物／資産／財産s from DateTextBox.xMinDate and xMaxDate. This was working 罰金 on （弁護士の）依頼人-味方する validation but not on server 味方する validation. Its now working in both 事例／患者s.
• When any of the numeric textboxes are 無能にするd or readonly by a FieldStateController, their spinners still worked if you 二塁打-clicked on them. They should be fully 無能にするd.
• EmailAddressValidator now supports the 選び出す／独身 引用する character in 指名するs on the left 味方する of the email 演説（する）／住所. The web.config とじ込み／提出する's Email 演説（する）／住所 表現 shown in the RegExpValidator's 表現 所有物／資産／財産 Editor does the same.
.
• IE Mac 5 has a bug in its 正規の／正選手 表現 parser that ignores 強調するs when the \w 表現 is used. \w should 許す 強調するs. This 原因（となる）s the EmailAddressValidator to fail on IE Mac 5 when the email 演説（する）／住所 含む／封じ込めるs an 強調する. Now the 正規の／正選手 表現 used explicitly 実験（する）s for an 強調する in the left 味方する of the email 演説（する）／住所. Also the web.config とじ込み／提出する's 正規の／正選手 表現 for Email 演説（する）／住所 has the same modification.

• DurationTextBox now supports a lead 無 on hours, に引き続いて your xDateTimeFormatInfo.ShortTimePattern or LongTimePattern. It also supports your TimeSeparator. 以前 it always used hh:mm and hh:mm:ss 判型s, ignoring your patterns.
• DateTextBox now 申し込む／申し出s the 所有物／資産／財産 xBlankMonthYearOnPopup. It 許すs you to define the month and year used to popup the calendar when the textbox is blank. 事前の to this 所有物／資産／財産, it would always popup using the month and year from xTodaysDate. It will still do that when unassigned.

• When the xDateTimeFormat.ShortDatePattern orders the year before the month on the MonthYearTextBox, any 入ること／参加（者） is considered 無効の. For example, with the Chinese culture using 'yyyy-M', no 入ること／参加（者） is 受託するd on the server 味方する.
• When the DateTextBox and TimeOfDayTextBox are connected and have a TimeTextBoxValidator 割り当てるd, using Ctrl+N showed the validator error message even though the data was valid. This only happens when DateTextBox is blank. This problem was introduced in v1.1.7.
• The UserAgent "Mozilla/5.0 (両立できる; Konqueror/3.2; Linux) (KHTML, like Gecko)" would 原因（となる） an exception.
• The stand-alone PopupCalendar 支配（する）／統制する and stand-alone PopupMonthYearPicker did not 保存する the selected date on the Mozilla-based browsers.
• The CS_Calendar 支配（する）／統制する was returning to the 初期の month shown after the page is submitted. (This was only a problem when the calendar updated months on the （弁護士の）依頼人 味方する and did not 自動車 地位，任命する 支援する on a month or date change.) It now returns to the month with the selected date, if there is one. That is the month that most likely was 見解（をとる）d when the page was submitted.
• The Mozilla browser (not its Netscape or FireFox 見解／翻訳／版s) would not filter keystrokes and would 報告（する）／憶測 javascript errors as you typed.
• Mozilla 1.4+, Netscape 7.1+, FireFox ran the keystroke 命令（する）s for Next/Prev Day/Month on DateTextBox twice, jumping by two. 味方する 影響 of a bug 直す／買収する，八百長をする in 1.1.7. (The Mozilla code base has a bug with / and ? characters that I'm 試みる／企てるing to work around.)
• Mozilla did not popup its normal 状況 menu where it should when a DateTextBox, TimeOfDayTextBox or DurationTextBox is on the page with its own 状況 or help menus. (This is 予定 to a design change in Mozilla that no longer matches the 公式の／役人 W3C spec. My code was working to spec.

• By default, the ButtonColumn 支配（する）／統制する (used in a DataGrid) always 生成するs buttons with the CausesValidation 所有物／資産／財産 始める，決める to 誤った. In other words, these buttons do not 実証する on the （弁護士の）依頼人-味方する and only 実証する on the server 味方する if you explicitly call 全世界のs.Page.実証する(). Now the VAM ButtonColumn 支配（する）／統制する has a CausesValidation 所有物／資産／財産 so you can take 支配（する）／統制する.
  Breaking change notice:It will default to 誤った to match the 存在するing functionality. If you have used a technique to 修正する the CausesValidation value of the button 支配（する）／統制する 含む／封じ込めるd in the ButtonColumn, this will break your code. You must switch to using the new 所有物／資産／財産.
• The PeterBlum.VAM.dll 議会 now supports the CLSCompliantAttribute.

• The Konqueror 3.2 browser 原因（となる）d an exception. Its UserAgent had some 予期しない formatting.
• Netscape 4.x browsers showed the error message when there is no error.
• Netscape 4.x browsers 生成するd （弁護士の）依頼人-味方する script code which 原因（となる）d a javascript error.
• The IntegerTextBox, DecimalTextBox and CurrencyTextBox 消費するd the ENTER 重要な, 妨げるing it from 圧力（をかける）ing the default button on the page.
• Using the FilteredTextBox with the \ character in the OtherCharacters 所有物／資産／財産 原因（となる）d a javascript error.
• When using a CheckBoxList or RadioButtonList with the RepeatLayout 所有物／資産／財産 始める，決める to "Flow", （弁護士の）依頼人 味方する validation always 示すd that there was an error when you use any validator or 条件 that 評価するs text. For example, CompareToValueValidator, RegexValidator, and CompareToStringsValidator.
• When using AlertImageErrorFormatter or HyperlinkErrorFormatter on a validator that only runs on the server 味方する, if the ErrorMessage 所有物／資産／財産 含む／封じ込めるs 選び出す／独身 引用するs ('), you would get a javascript error after 地位，任命する 支援する when an error should be shown.
• CombinedErrorMessages 支配（する）／統制する incorrectly disappeared after a 地位，任命する 支援する, where the server 味方する 追加するd some error messages from CustomValidators that are using OverrideClientSideEvaluation. It also happened when the validators are all server-味方する only.
• When using a CustomValidator with ControlToEvaluate unassigned, a （弁護士の）依頼人-味方する evaluation method, an AlertImageErrorFormatter and the 全世界のs.Page.FocusAfterAlert = true, a javascript error occurred when the error is shown.
• When a CustomValidator has nothing 割り当てるd to ControlIDToEvaluate/ControlToEvaluate, it would not appear on the （弁護士の）依頼人-味方する ValidationSummary. It would appear after a 地位，任命する 支援する creates the ValidationSummary.
• When using a Microsoft Button or Microsoft ImageButton that is 登録（する）d with the 全世界のs.Page.RegisterSubmitControl method and it has CausesValidation=誤った, calls to 全世界のs.Page.実証する() are necessary to manually 成し遂げる validation. However, 予定 to an incorrect group 指名する passed 支援する to the server 味方する, 全世界のs.Page.実証する() does not 実証する anything. This also 影響する／感情s the VAM ButtonColumn which uses the Microsoft buttons and RegisterSubmitControl() method.
• The PeterBlum.VAM.全世界のs.Page.ConfirmMessageGroup 所有物／資産／財産 did not work when 割り当てるd to text that 含む／封じ込めるd any lowercase characters.
• When PeterBlum.VAM.全世界のs.Page.TextHiliteFieldsCssClass or NonTextHiliteFieldsCssClass are "" and other 所有物／資産／財産s associated with submitting a page were at their default, two problems occured. Any CombinedErrorMessage 支配（する）／統制する would hide its error message when you clicked 服従させる／提出する. The VAMPage.PostValidationUpdateScript 機能（する）／行事 would not 遂行する／発効させる.
• When you have a ValidationSummary and you have written javascript that calls form.reset(), the ValidationSummary will appear then disappear after a postback.
• When using the Reset button with PeterBlum.VAM.全世界のs.Page.ShowAlertOnSubmit=true, some 条件s will show the 警報 when Reset is clicked. No 警報 should appear.
• There is an incompatibility between ASP.NET Design 方式 Extender (ADME) and Microsoft's 報告（する）／憶測ing Services within Visual Studio.逮捕する. When there is an open 報告（する）／憶測ing Services 事業／計画（する） with the ADME VS.NET 追加する-in 任命する／導入するd, Intellisense stops working. Microsoft has 決定するd the source of the problem within the 報告（する）／憶測ing Services code and 供給（する）d a simple workaround which is in this build. If you 遭遇（する） the problem, please follow these steps:
  1. 出口 VS.NET
  2. In 追加する/除去する Programs, 除去する ASP.NET Design 方式 Extender
  3. Return to VS.NET. The ADME button and 道具s menu 命令（する） should still be there. Click on each and answer Yes to 除去する the 命令（する）.
  4. 出口 VS.NET again
  5. Run the installer from C:\program とじ込み／提出するs\Professional Validation And More\ADME Installer.
  6. Open VS.NET. 確認する the ADME button and 道具s menu 命令（する）. 確認する that selecting the 命令（する） opens ADME Settings Editor.
  7. 実験（する） against 報告（する）／憶測ing Services to 確認する Intellisense now 作品.
  
• The MSStyle Validators (used when you use the 変える Page to VAM.exe program) ignored the 明白な 所有物／資産／財産 when it is 始める，決める to 誤った. It always shows 明白な as true.

• QuickDateMenu now has an 自動車 地位，任命する 支援する feature. Use the xAutoPostBackB 所有物／資産／財産 and optionally 体制／機構 a server 味方する event handler in the OnSelection event.
• QuickDateMenu now can be 割り当てるd to the MonthYearTextBox and AnniversaryTextBox.
• When any textbox has a 命令（する） invoked, it now 解雇する／砲火／射撃s the onchange event 権利 away, updating 関係のある 支配（する）／統制するs 含むing validators.
• Support for these 議会s in 部分的な／不平等な 信用 環境s, 含むing the AllowPartiallyTrustedCallersAttribute and documentation of 要求するd 権利s.
• IE 6 browsers had a 制限. You couldn't use a !DOCTYPE that 設立するd a "compatibility 方式" of CSS1Compatibility, such as using the XHTML notation. The 制限 妨げるd the popups from appearing in the 訂正する 場所 when the page was scrolled. I've 設立する a 解答 permitting other !DOCTYPES. However, this does not mean these 支配（する）／統制するs are XHTML compliant. That cannot happen until ASP.NET itself is XHTML compliant, coming in ASP.NET 2.0.

• When a DateTextBox had both xFocusOnError=true and xErrorAlertOnChange=true, if you entered a date that omits date separators and there was an error, you would get the 警報 box twice.
• Mozilla 1.4+ and Netscape 7.1+ broke how 削除する characters are 扱うd in onkeypress events. (Their 前任者s and all other browsers work.) As a result, you couldn't type a 削除する into the DateTextBox. This is 直す／買収する，八百長をするd.
• When DateTextBox.xAutoPostBackB is true and the 使用者 selected any 命令（する） from the 状況 or help menus (except Popup Calendar), the 命令（する） should 自動車 地位，任命する 支援する when done. It did not.
• When DateTextBox.xAutoPostBackB is true and the 使用者 types the keyboard 命令（する） to popup the calendar, the calendar popped up but the page 地位，任命するd 支援する 権利 away.
• When TimeOfDayTextBox or DurationTextBox.xAutoPostBackB is true, a JavaScript error may have occurred. The 自動車 地位，任命する 支援する script had an error which 妨げるd it from 遂行する／発効させるing.
• Introduced in v1.1.6: DataGrids 報告（する）／憶測d an error that a 支配（する）／統制する has a bad 所有物／資産／財産 when they 含む／封じ込める any of the TextBoxes.
• When a browser 供給（する）d no HTTP_USER_AGENT string, you can get an "反対する 言及／関連 not 始める，決める to an instance of an 反対する." exception. This is a second 事例／患者. (An earlier 事例／患者 was 直す／買収する，八百長をするd in 1.1.6.)
• When there is a date 範囲 適用するd to the MonthYearPicker, it was possible to be 行方不明の the 権利 arrow to scroll to the last year of the 範囲. The 使用者 would not be able to get to that one year if it is the first year of the next group of years. DateTextBox, MonthYearTextBox and CS_Calendar all support MonthYearPicker with date 範囲s.
• When there is a date 範囲 適用するd to the MonthYearPicker and the 現在の year is at the end of the 範囲, the some of the months were 無能にするd. As you clicked on the arrows, the selected year changed but the months remained 無能にするd. They now 反映する the months 利用できる to the selected year.
• When using the ContextMenu 支配（する）／統制する for 権利 clicks on the whole page, a 権利 click on the page resulted in a javascript error before the menu popped up.
• When using CS_Calendar with a browser that only supports the server-味方する calendar (xTrueBrowser.xSupportsCalendar=誤った, such as IE Mac 5.2, Netscape 4, and オペラ 6), the OnDateChanged and OnMonthViewChanged event handlers did not 解雇する／砲火／射撃.
• Introduced in 1.1.6: When using the xAutoAbsPositionModeB 所有物／資産／財産, some 状況／情勢s would 原因（となる） a NullReferenceException on any of the textboxes.
• When using SpecialDates on a CS_Calendar to 供給（する） a tooltip to a date 独房, the tooltip was shown on 独房s that were blank (out of 範囲, hidden) when the calendar is in server-味方する 方式. (xTrueBrowser.xSupportsCalendar=誤った)
• When you created a DateTextBox programmatically and 接近d xPopupCalendar or xContextMenu 所有物／資産／財産s before 追加するing the 支配（する）／統制する to the page's 支配（する）／統制する tree, the calendar and 状況 menu both would be 抑えるd. 類似して, if the DateTextBox was in a DataGrid and you 接近d the same 所有物／資産／財産s in the ItemCreated event, you had the same 影響. You no longer have to use workarounds to 解決する them.
• Browsers built on the Mac OS X 壇・綱領・公約 that 利用する "AppleWebKit" (the engine of Safari) would throw an exception when （悪事，秘密などを）発見するd. Now they will not. Commercially, only OmniWeb 4.5 was 影響する／感情d however, 使用者s developing their own code could get errors too. (Apple's Safari always worked.)

• ValidationSummary has a new 所有物／資産／財産, RelatedControl_InvisiblePreservesSpace. When using the RelatedControlID feature, this 決定するs if the 関係のある 支配（する）／統制する 保持するs the space or not while invisible. See page 134 of the 使用者's Guide.
• 追加するd two 正規の／正選手 表現s to the 所有物／資産／財産 Editor for the 表現 所有物／資産／財産 on RegExpValidator and RegExpCondition: Canadian 郵便の Code and US & Canadian 郵便の Codes.
• CurrencyTextBox, IntegerTextBox, DecimalTextBox and FilteredTextBox now have the popup text editor associated with their ToolTip 所有物／資産／財産 in the 所有物／資産／財産s Editor. This 許すs entering 非常に長い text easily. FilteredTextBox now has the same editor on its Text 所有物／資産／財産 too.
• FieldStateControllers now 扱う CheckBoxLists and RadioButtonLists better by updating the 内部の radiobuttons/checkboxes with the visibility, enabled, and CssClass 所有物／資産／財産s of ConditionTrue and ConditionFalse. 以前 they only updated the enclosing HTML tag around those buttons which didn't 扱う Enabled 明言する／公表するs 井戸／弁護士席, 特に on 非，不，無-IE browsers.
• Validators have an optimized system for managing the ViewState so that only the items you really want to 蓄える／店 are kept. See the ViewStateMgr 所有物／資産／財産 on the validator 支配（する）／統制するs. See page 123 of the 使用者's Guide for 詳細（に述べる）s.
• Support for these 議会s in 部分的な／不平等な 信用 環境s, 含むing the AllowPartiallyTrustedCallersAttribute and documentation of 要求するd 権利s. See page 28 of the 取り付け・設備 Guide for 詳細（に述べる）s.
• In 準備 for ASP.NET 2.0 ("Whidbey"), any HTML 生成するd within VAM is XHTML compliant, with the exception of the spinners on CurrencyTextBox, IntegerTextBox, and DecimalTextBox. Any HTML 生成するd using Microsoft's 支配（する）／統制するs and classes remains HTML 4 and not XHTML compliant. The 期待 is that if you use VAM 2.0.1 with Whidbey, the VAM 支配（する）／統制するs will be compliant. This remains to be proven.
• If you 追加する to the FSC.ExtraControlsToRunThisAction, Val.ExtraControlsToRunThisAction, MultiFSC.ControlConnections, or CombinedErrorMessage.Validators 所有物／資産／財産s programmatically, you no longer are 要求するd to create ControlConnection 反対するs to 追加する. Instead, the 追加する() method has been 積みすぎる to 許す passing just the 支配（する）／統制する ID or 言及／関連 that you want to use. VAM will 人物／姿／数字 out the 残り／休憩（する） for you.

• When using an <input type=とじ込み／提出する runat=server > 支配（する）／統制する, the 大（公）使館員d validators 解雇する／砲火／射撃d on a click in the textbox. They now 解雇する／砲火／射撃 on a change to the textbox.
• When the EmailAddressCondition, CharacterCondition, or CompareToStringsCondition was within a MultiConditionValidator, the MultiConditionValidator did not 生成する the （弁護士の）依頼人-味方する validation code.
• When using a CustomValidator, if you did not 割り当てる 割り当てる ControlIDToEvaluate, ControlToEvaluate, SecondControlIDToEvaluate or SecondControlToEvaluate, you would get a NullReferenceException on 地位，任命する 支援する.
• When using a CustomValidator and you 始める，決める the ErrorMessage 所有物／資産／財産, it was not 反映するd when a ValidationSummary appears before that validator. Happened only in the server 味方する validator. The （弁護士の）依頼人-味方する wasn't 影響する／感情d by this.
• Any validator whose DataType 所有物／資産／財産 is 始める，決める to "Integer" 扱う／治療するd values that 越えるd the 限界s of Int32 as valid on the （弁護士の）依頼人-味方する until the number 越えるs Int64 範囲. The server-味方する caught these 過度の values.
• When using the OtherCharacters 所有物／資産／財産 in CharacterValidator, CharacterCondition or FilteredTextBox and you enter '-' (minus character), errors could occur. They 含むd javascript errors, server 味方する Regex exceptions, and 潜在的に 無効の values getting through.
• The 正規の／正選手 表現 for U.S. 郵便の Code shown in the 所有物／資産／財産s Editor had an error. It would not 報告（する）／憶測 an error when the first 5 digits were 訂正する but the "+4" part was incorrect. For example, these were valid: 55555-, 55555-1, 55555-d. Be sure to 取って代わる the VAM.config とじ込み／提出する in your [webapp]\VAM folder. Additionally, any RegExpValidator using this 表現 should be updated with the new 表現. (This does not happen automatically.)
• Design 方式 did not update the "Select a Pattern" 命令（する）'s 正規の／正選手 表現s 名簿（に載せる）／表（にあげる） after you saved or 削除するd an 表現 within the 表現 所有物／資産／財産 Editor.
• The AlertImageErrorFormatter.ToolTipLookupID was ignored. String Lookups did not occur.
• When CurrencyTextBox uses ShowThousandsSeparator and the 現在の culture has NumberFormatInfo.NumberDecimalDigits <> NumberFormatInfo.CurrencyDecimalDigits, the 初期の value 割り当てるd to the DoubleValue 所有物／資産／財産 would 反映する the NumberDecimalDigits. It now 反映するs CurrencyDecimalDigits.
• When the DecimalTextBox has the CultureInfo.NumberFormat.NumberDecimalDigits = 0, ShowThousandsSeparator=true, and its TrailingZeroDecimalPlaces 所有物／資産／財産 始める，決める to 無, a 追跡するing decimal place remained as the page was 最初 shown.
• When the CurrencyTextBox uses AllowExtraDecimalDigits=true and the CurrencyDecimalSeparator is not a period, formatting problems appeared after the text was reformatted on the （弁護士の）依頼人-味方する.
• The MultiFieldStateController 原因（となる）d the browser to hang when ExtraControlsToRunThisAction was used. 結局 IE put up an error message about stopping a script.
• When using a MultiFieldStateController that changed the Enabled or Visibility 明言する／公表する, on 地位，任命する 支援する, Validation didn't know the 訂正する 明言する／公表する and would 実証する incorrectly. (This was not a problem in the FieldStateController.)
• When FieldStateController.UseValidationGroup is true, the page was prevalidated as it is opened, as if you clicked 服従させる／提出する. This should not happen. If you want the page to be prevalidated, call PeterBlum.VAM.全世界のs.Page.実証する() on the server 味方する.
• MultiFieldStateController did not initialize the 支配（する）／統制するs to their 明言する／公表する settings during page 負担.
• FieldStateControllers had difficulty with changing CheckBox and RadioButton 支配（する）／統制するs when they 始める，決める them invisible or 無能にするd 最初. This is 予定 to an unusual HTML 生産（高） on these 支配（する）／統制するs that 令状s the 無能にするd or style=visibility:hidden せいにするs into an enclosing <（期間が）わたる> tag so that they could 適用する to the label too. Now the code （悪事，秘密などを）発見するs these 支配（する）／統制するs and updates both the enclosing <（期間が）わたる> tag and the tag for the checkbox or radiobutton. 公式文書，認める: This is not connected to CheckBoxLists and RadioButtonLists which are 扱うd in another change in this 解放（する）.
• When using the String Lookup System with either the RequiredFieldDescriptor or RequiredFieldMarker for localization, if you 地位，任命する 支援する and switch cultures, the text did not 反映する the new culture. The ViewState had to be enabled for this error to occur.
• When a 服従させる／提出する button was associated with Page.RegisterSubmitButtonToDisable(), if the button.明白な=誤った, a javascript error would occur.
• 使用者s of Infragistics UltraWebGrid v3.0 who 追加するd their grid to a UserControl (or other 指名するing コンテナ) would get a javascript error. The 直す／買収する，八百長をする 要求するs that you have UltraWebGrid 3.0.20041.11 or higher. In 新規加入, the 強調する character is no longer permitted in the ID of the UltraWebGrid 支配（する）／統制する and any 含む／封じ込めるing 指名するing コンテナ. See page 124 of the 使用者's Guide for 詳細（に述べる）s.
• When using the VAM EditCommandColumn 支配（する）／統制する within a DataGrid, if any of the buttons are invisible, you would get a javascript error.
• The CombinedErrorMessages 支配（する）／統制する showed the incorrect messages when there were two or more of these 支配（する）／統制するs on the page.
• Browsers built on the Mac OS X 壇・綱領・公約 that 利用する "AppleWebKit" (the engine of Safari) would throw an exception when （悪事，秘密などを）発見するd. Now they will not. Commercially, only OmniWeb 4.5 was 影響する／感情d however, 使用者s developing their own code could get errors too. Apple Safari was already working 正確に.

• New validator: CreditCardNumberValidator (and CreditCardNumberCondition). Reviews the patterns in credit card numbers to 確認する they match basic 支配するs of credit card numbers.
• New validator: CharacterValidator (and CharacterCondition). 確認するs that every character in a text field is in a 始める，決める of characters that you 明示する.
• New validator: EmailAddressValidator. Aside from 実証するing the character pattern on the （弁護士の）依頼人 and server 味方する, it can be 麻薬中毒の up to 前進するd Intellect's AspNetMX email 演説（する）／住所 validation engine to 確認する the existance of the domain and even the actual email 演説（する）／住所. AspNetMX is a separate 製品 利用できる at www.aspnetmx.com.
• New textbox: FilteredTextBox. Filters out characters that you don't want as the 使用者 types.
• New 支配（する）／統制する: CombinedErrorMessages. Now you can 取って代わる individual Error Formatters on each validator with a 選び出す／独身 Error Formatter. 除去するs the clutter when 多重の error messages are shown as now they appear as a 選び出す／独身 piece of text under one error formatter. For example, an Image with 警報 Error Formatter will 名簿（に載せる）／表（にあげる） all error messages associated with a particular field in the 警報 box. You 決定する how the error messages are separated: by line breaks or text separators.
• The new 全世界の Settings Editor 使用／適用 供給するs a Windows UI to edit the custom.VAM.config とじ込み／提出する. It supports the <GlobalProperties> and <StringLookup> sections of that とじ込み／提出する.
• The IntegerTextBox, DecimalTextBox and CurrencyTextBox now support an optional Spinner 支配（する）／統制する. A spinner is a pair of arrows to the 権利 of the text box that increment and decrement the value.
• New error formatter: HyperLinkErrorFormatter ("Hyperlink with 警報"). A hyperlink that when clicked, shows an 警報 with the message. A 広大な／多数の／重要な way to 減ずる the page size while using a familiar metaphor to click.
• The new HiliteFields feature 許すs other 支配（する）／統制するs to change their style when a validation error is shown. For example, change the font color of the field label or the background color of an enclosing <DIV>. This is another way to catch the 使用者’s attention.
• Validators and FieldStateControllers have a new 所有物／資産／財産, ExtraControlsToRunThisAction. This 許すs you to introduce more 支配（する）／統制するs that when clicked or changed, run the validator or fieldStateController. On the FieldStateController, it 取って代わるs the 所有物／資産／財産s ControlIDToRunThisAction and ControlToRunThisAction. Any 存在するing code will continue to work but its 変えるd to the new 所有物／資産／財産 at runtime. In design time, you will no longer see ControlIDToRunThisAction in the 所有物／資産／財産 Editor.
• DecimalTextBox has a new 所有物／資産／財産, TrailingZeroDecimalPlaces, that 決定するs if 付加 追跡するing 無s are 追加するd. It can also 除去する the decimal part when the value equals a whole number.
• CurrencyTextBox has a new 所有物／資産／財産, HideDecimalWhenZero, that 決定するs if the decimal part is shown when the value is a whole number. When used, the text "12.00" will be reformatted as "12" while "12.1" will reformat as "12.10".
• ValidationSummary now 申し込む／申し出s the 所有物／資産／財産 ScrollIntoView.
• Validators no longer 要求する that you 始める，決める Enabled=誤った when the ControlToEvaluate is 始める，決める to 明白な=誤った. Instead, they automatically 行為／法令／行動する as if Enabled is 始める，決める to 誤った.
• 変える Pages To VAM.exe now 変えるs the datagrid's EditCommandColumn and ButtonColumn classes.
• The RegexValidator and RegexCondition now have the 所有物／資産／財産 IgnoreBlankText. It 決定するs how to 扱う／治療する blank text. When true, blank text is not 評価するd (like it does now and like Microsoft's RegularExpressionValidator does.) When 誤った, blank text is 扱う／治療するd as an error.
• The page level setting ConfirmMessage now supports localization and string lookups using the new ConfirmMessageLookupID 所有物／資産／財産.
• CustomConditions, CustomValidators and any validator that uses the ServerCondition 所有物／資産／財産 now support the ability to change the ErrorMessage and SummaryErrorMessage within your custom 条件, on both the （弁護士の）依頼人 and server 味方する.
• Support for Infragistics UltraWebGrid.
• Easily support third party textboxes, checkboxes, radiobuttons, listboxes, and dropdownlists that were not subclassed from their Microsoft 同等（の）s and do not support the ValidationPropertyAttribute. (VAM already 扱うs the 残り／休憩（する）.)
• Support for （弁護士の）依頼人-味方する validation on third party （弁護士の）依頼人-味方する menu 支配（する）／統制するs. When a menu 命令（する） is selected that you want to 地位，任命する 支援する, you can have it run （弁護士の）依頼人-味方する validation first. (You could always 体制／機構 server-味方する validation on anything that 地位，任命するs 支援する.)
• Use the new 全世界のs.Page.SubmitOrder 所有物／資産／財産 to 決定する the order of these three 活動／戦闘s that occur when the page is submitted: validation, 確認する message (when using the ConfirmMessage 所有物／資産／財産), custom 服従させる／提出する 機能（する）／行事 (when using the CustomSubmitFunctionName 所有物／資産／財産.)
• Use the new 全世界のs.Page.FocusAfterAlert 所有物／資産／財産 to 始める，決める 焦点（を合わせる） to the field with the error after the 使用者 invokes the 警報 box on the Image With 警報 (AlertImageErrorFormatter) and HyperLink With 警報 (HyperLinkErrorFormatter) error formatters.
• Use the new 全世界の 所有物／資産／財産s DefaultRequiredFieldToolTip and DefaultRequiredFieldToolTipLookupID to 設立する a default tooltip for the RequiredFieldMarker 支配（する）／統制する. For example, have a 道具 tip that says, “要求するd”.
• Use the new 全世界のs.Page.SetFocusFunctionName to 中継 a （弁護士の）依頼人-味方する 機能（する）／行事 that is called whenever 焦点（を合わせる） is 始める，決める to the field 存在 評価するd.

• The CurrencyTextBox.AllowExtraDecimalDigits 所有物／資産／財産 did not get 移転d to a DataTypeCheckValidator that 監視するs the CurrencyTextBox's 判型.
• The 専攻するd TextBoxes showed the readonly 所有物／資産／財産s IsEmpty and IsValid in the 所有物／資産／財産s Editor. They are no longer shown.
• When any of the に引き続いて 条件s are 含む／封じ込めるd in the MultiCondition, the browser may 報告（する）／憶測 a JavaScript error because they didn't get a chance to 宣言する their VAM_XVF.js script とじ込み／提出する: DifferenceCondition, CountSelectionsCondition, CountTrueConditions, and any 専攻するd 条件.
• When using the VAMPage.CustomSubmitFunctionName, your 機能（する）／行事 is incorrectly passed an 反対する, not the group 指名する string as 約束d in the docs. Now it passes the group 指名する string.
• When a browser's UserAgent is not 供給（する）d, you can get a NullReferenceException in the TrueBrowser.GetTrueBrowser method.
• ValidationSummary.HyperLinkToField jumps to the field in an Enabler 条件 instead of the validator's ControlIDToEvaluate.
• DecimalTextBox 一連の会議、交渉／完成するd to one decimal place when you 割り当てるd a value to its DoubleValue 所有物／資産／財産.

• Design change: TimeOfDayTextBox and DurationTextBox now 申し込む／申し出 the xOnChangeFunctionName 所有物／資産／財産 where you can 中継 a JavaScript 機能（する）／行事 to run when either of these textboxes 解雇する／砲火／射撃 the onchange event.
• Design change: Licensing 体制／機構 is much easier. You can 割り当てる Web Server and 場所／位置 Licenses once, in Application_Start, and 議席数是正 Licenses once per page in Page_Load. Continues to support 遺産／遺物 licensing 体制／機構 with the xLicensing 所有物／資産／財産 on each 支配（する）／統制する. If you use the new 体制／機構, it will 無視／無効 the xLicensing 所有物／資産／財産. See the 使用者's Guide, page 45, for 詳細（に述べる）s on switching to the new model.
• Design change: All date and time textboxes now automatically position their calendar icon and help button when placed on the GridLayout design 方式 surface of Visual Studio.逮捕する. 以前 you would have to enclose the 支配（する）／統制する in an 絶対 positioned <div> or <（期間が）わたる> tag. See the new 所有物／資産／財産 xAutoAbsPositionModeB in the 使用者's Guide. It defaults to 存在 enabled. If you already have 体制／機構 your textbox 正確に, you will NOT need to change anything.
• Design change: TimeOfDayTextBox and DurationTextBox now 申し込む／申し出 the ApplyRounding() method. Use it after you 割り当てる an unrounded time value and want the 支配（する）／統制する to 適用する the 一連の会議、交渉／完成するing 支配する of xRoundUpMinutes.
• Design change: CS_Calendar 申し込む／申し出s new 所有物／資産／財産s to show any text or HTML that you want in the footer. (Change 影響する／感情s DateTextBox and PopupCalendar 支配（する）／統制するs.)
• Enhancement: 使用者s Guide now 文書s the JavaScript 機能（する）／行事s useful for working with TimeOfDayTextBox and DurationTextBox.
• When the TimeOfDayTextBox or DurationTextBox have style=visibility:hidden, an 大（公）使館員d arrow button 支配（する）／統制する still appears.
• TimeOfDayTextBox and DurationTextBox arrow buttons 答える／応じる more 自然に to 二塁打-clicks.
• Internet Explorer 4 for Windows 報告（する）／憶測s a JavaScript error on any 支配（する）／統制する with a popup element.
• When the MonthYearPicker is in a UserControl or パネル盤 and has its xMonth and xYear 所有物／資産／財産s 割り当てるd, clicking on a different month or year results in a JavaScript error.
• When a browser 供給（する）s no HTTP_USER_AGENT string, you can get an "反対する 言及／関連 not 始める，決める to an instance of an 反対する." exception.
• When using the PDPToVAM's UnselectableDatesValidator, it does not 適切に 実証する on the （弁護士の）依頼人-味方する on the Internet Explorer for the Mac browsers.
• When setting the DateTextBox 所有物／資産／財産 xShowPopupB to 誤った in the 所有物／資産／財産s Editor, it no longer 追加するs an extraneous "明白な=誤った" into the section of the ASP.NET text.

• IgnoreConditionValidator. This new validator is very 類似の to a CustomValidator. However, instead of putting your validation code in an event handler, you can let your validation code be part of your logic to save data. This 避けるs splitting your code. See page 40 of the 使用者's Guide.
• You can have VAM automatically 無能にする 服従させる／提出する buttons after they are clicked, to 妨げる the 使用者 from submitting the page twice using the new PeterBlum.VAM.全世界のs.Page.RegisterSubmitButtonToDisable method. 始める，決める page 88 of the 使用者's Guide.
• ValidationSummary has a new 所有物／資産／財産, ListLeadImageURL. This makes it 平易な to use an image in 前線 of each error message when the DisplayMode = 名簿（に載せる）／表（にあげる）. See page 98 of the 使用者's Guide.
• The DataGrid's EditCommandColumn and ButtonColumn 含む／封じ込める Microsoft buttons and are very difficult for 使用者s to use VAMPage.RegisterSubmitControl to make those buttons work with VAM. VAM now 含むs subclasses of the EditCommandColumn and ButtonColumn, PeterBlum.VAM.EditCommandColumn and PeterBlum.VAM.ButtonColumn, that 訂正する these problems. See "Supporting the DataGrid", page 106 of the 使用者's Guide.
• 専攻するd TextBoxes now have several JavaScript 機能（する）／行事s to 補助装置 you in 令状ing code that gets and 始める，決めるs values on the （弁護士の）依頼人-味方する. The 使用者's Guide 詳細（に述べる）s it, along with examples. See page 123, "答える／応じるing to （弁護士の）依頼人-味方する Changes".
• The 変える Pages to VAM.exe 公共事業（料金）／有用性 now supports 使用者 支配（する）／統制する (*.ascx) とじ込み／提出するs.
• The 供給（する）d gif image とじ込み／提出するs 'requireddot.gif' and 'valerroricon.gif' have been 修正するd to support a transparent background. They 以前 had a white background. Copy these とじ込み／提出するs from the [VAMInstallation]\VAM\外見 folder to your [webapp]\VAM\外見 folder, if you want these updates.
• When 全世界のs.Page.BlinkOnSubmit 許すs blinking, when a page 地位，任命するs 支援する and then redraws with errors shown, those errors will blink. This 許すs server 味方する validation of a custom validator to still 利益 from blinking as they show their error.
• Validators and 条件s have a new 所有物／資産／財産, OverrideClientScriptEvaluation. This is best for custom validators and IgnoreConditionValidator to show their error 最初 after 地位，任命する 支援する but as the 使用者 changes the associated field or 服従させる／提出するs, （弁護士の）依頼人-味方する will hide the error message. This 許すs a 限られた／立憲的な （弁護士の）依頼人-味方する interface when you don't 令状 your own for your custom validation 条件s. See "（弁護士の）依頼人-味方する 条件" on page 55 of the 使用者's Guide.
• New method on the VAMPage 反対する, RegisterChildSubmitControls. It is a companion to VAMPage.RegisterSubmitControl that 登録（する）s all 服従させる／提出する 支配（する）／統制するs 含む／封じ込めるd within any 支配（する）／統制する you 供給（する）. See "Buttons and 支配（する）／統制するs To 服従させる／提出する the Page" on page 45 of the 使用者's Guide.

• Pages that run from a call to Server.移転 did not 体制／機構 the （弁護士の）依頼人-味方する 部分s of VAM and often 生成するd scripting errors. See the new topic "Using Server 移転" around page 138 of the 使用者's Guide for directions on using Server.移転.
• The MS-Style Validators did not 扱う the 事例／患者 when the Text 所有物／資産／財産 gets its value from the "inner text". This is how VS.NET 始める，決めるs this 所有物／資産／財産. It usually is a problem for 使用者s of the 変える Pages To VAM.exe program. If you already have a "Text" 所有物／資産／財産 written into the せいにするs of a 支配（する）／統制する, it will 報告（する）／憶測 an error. 除去する that 所有物／資産／財産 and 再任命する the text to the inner text (between start and end tags.)
• When a validator, fieldstatecontroller, or 専攻するd textbox is 含む／封じ込めるd within another 支配（する）／統制する that is 明白な=誤った, an exception was thrown 示すing a 所有物／資産／財産 like ControlIDToEvaluate is incorrectly 始める，決める.
• The PeterBlum.VAM.LinkButton did not run （弁護士の）依頼人-味方する validation.
• When the ValidationSummary is on the page but there are no validators or other VAM 支配（する）／統制するs, a JavaScript error appeared.
• When the FieldStateController or MultiFieldStateController is Enabled=誤った, on 地位，任命する 支援する, it threw an exception if one of the 支配（する）／統制するs it's 大（公）使館員d to (ControlIDToChange or ControlConnections) was 始める，決める to 明白な=誤った.
• The 全世界のs.DefaultControlErrorCssClass 所有物／資産／財産 was not copied to each page's ControlErrorCssClass 所有物／資産／財産.
• The {LABEL} 記念品 did not 成し遂げる a string lookup when the Label.LabelControlID 所有物／資産／財産 pointed to a LocalizableLabel. It only gets the label's Text 所有物／資産／財産. It now supports LocalizableLabel.
• When a TextBox was 始める，決める in Password 方式, validators were 解雇する／砲火／射撃d when you click on the textbox. They now 解雇する／砲火／射撃 when the textbox changes.
• When using the ErrorFormatter.GapBeforeType 所有物／資産／財産 始める，決める to "Pixel", the <img> tag 言及／関連s a とじ込み／提出する in [webapp]/VAM/外見s/. It now also supports the 使用者 defined path in web.config's VAM_AppearanceVirtualPath 重要な.
• When the Culture 明示するd NumberFormat.NumberGroupSeparator = "" or NumberFormat.CurrencyGroupSeparator = "", you would get a runtime error or a JavaScript error.
• The ErrorFormatter.GapBefore 所有物／資産／財産 was supposed to show a gap only when the error message is shown. The gap showed all the time.
• When retrieving a value from IntegerTextBox.IntegerValue, DecimalTextBox.DoubleValue, or CurrencyTextBox.DoubleValue, if the text is not 正確に formatted, these could throw a "Null 反対する" exception. They now throw a FormatException instead.
• When using a culture whose DecimalSeparator was not a period (.), the DecimalTextBox and CurrencyTextBox would throw an exception as you retrieve the value from the DoubleValue 所有物／資産／財産.
• The ValidationSummary 支配（する）／統制する always showed the HyperLinksToolTip, even when HyperLinkToFields was 誤った. It shouldn't show in that 事例／患者.
• When using either FocusOnChange or FocusOnSubmit and you have a richtextbox that is 存在 実証するd, you would get a JavaScript error after it 実証するs. Some richtextboxes use a hidden input field and that element is associated with the ControlIDToEvaluate. Its 違法な to 始める，決める 焦点（を合わせる） on a hidden input field.
• When a browser 供給（する）s no HTTP_USER_AGENT string, you would get an "反対する 言及／関連 not 始める，決める to an instance of an 反対する." exception on a call to GetTrueBrowser().
• When the Enabler 所有物／資産／財産 was 始める，決める with a 条件 that 含むs the DataType 所有物／資産／財産, you would get a JavaScript error: "反対する doesn't support the 所有物／資産／財産 or method" when the validator 評価するs.
• Gecko-based browsers (Netscape 6+, Mozilla) did not filter 違法な keystrokes on the 専攻するd TextBoxes.
• オペラ 7 did not reformat the DecimalTextBox.
• RequiredTextValidator and RequiredTextCondition now supports the System.Web.UI.WebControls.RadioButtonList. It should compare to the ListItem.Value of the selected 無線で通信する button. (Microsoft's RequiredFieldValidator does this.) Worked 適切に on the server 味方する but not the （弁護士の）依頼人-味方する.
• When using the web.config setting VAM_AppearanceVirtualPath, it did not work when the string did not match "~/VAM/外見" with 事例／患者 insensitivity.

• Design change: 含むs support for Professional Validation And More, another 製品 of PeterBlum.com. There are many new things you can do with the VAM-style 見解／翻訳／版s of the validators. See the とじ込み／提出する "VAM Style Validators.pdf" for 詳細（に述べる）s.
• Design change: New 所有物／資産／財産, xAutoSharedCalendarB, makes it easier to 体制／機構 a 株d calendar between さまざまな DateTextBoxes. Its 特に helpful if you use the DateTextBox on a DataGrid, DataList or Repeater.
• When CS_Calendar.xEnableMonthYearPickerB is 誤った and you are running on an IE/勝利，勝つ browser, typing "M" (the shortcut for Month Year Picker) 生成するs a JavaScript error.
• v1.1.4 broke the MonthYearTextBox. It ignores any year you enter, always using the 現在の year.
• v1.1.4 turned off the popup calendar on IE/Mac 5 browsers. It has been 回復するd for IE 5.0-5.1. It should be off for IE/Mac 5.2.
• When you 始める，決める the BackColor or ForeColor 所有物／資産／財産 on the MonthYearPicker, that color doesn't 移転 into the month and year （米）棚上げする／（英）提議するs.
• When you 始める，決める style 所有物／資産／財産s on the 状況 menu of CS_Calendar (xContextMenu.ForeColor, for example) and have at least two DateTextBoxes or CS_Calendars with this setting, you will get a runtime error for FindControl 報告（する）／憶測ing the 支配（する）／統制する "_CM" is duplicated on the page.
• When you 始める，決める the ForeColor せいにする on the 状況 menu of CS_Calendar, it doesn't 適用する. The page's default forecolor is used.
• When you 体制／機構 an 代案／選択肢 path to a folder in the web.config とじ込み／提出する and it starts with a tilde, a 二塁打-削除する will appear in the script とじ込み／提出する path if you move the web.config とじ込み／提出する to a server whose domain is the actual web app. This can 原因（となる） javascript errors.
• When you use CS_Calendar.xIsEmpty before 言及／関連ing CS_Calendar.xSelectedDate, xIsEmpty returns true even when there is a selected date.
• When there are no 状況 or help menus from any PDP 支配（する）／統制する on the page and you have a DateTextBox within a <DIV style="OVERFLOW:自動車;">, the calendar may popup in the wrong place when the area is scrolled.

• Design change: Now supports Safari v1.0 browser (Apple). Previous 見解／翻訳／版s were fully 相いれない 生成するing a runtime error on the page. Aside from getting rid of the runtime error, 非常に／多数の changes were made to the scripts to get this browser to work. The Safari 1.0 (85) browser is still a very buggy 壇・綱領・公約 and Peter's Date 一括 will 論証する some of those bugs when workarounds were not 設立する. Click here for 詳細（に述べる）s.
• Design change:CS_Calendar has a new 所有物／資産／財産, xDayCellBorderSides. When you are showing 国境s and WeekRowCellSpacing is 0, you 普通は see a grid of lines. This 所有物／資産／財産 lets you show only 水平の or vertical lines for unique visual 影響s.
• Netscape 4 stopped 扱うing （弁護士の）依頼人-味方する reformatting and validation of the DateTextBox (not using validator 支配（する）／統制するs but the 内部の code of the DateTextBox).
• Netscape 4 stopped 扱うing （弁護士の）依頼人-味方する reformatting validation of the TimeOfDayTextBox and DurationTextBox (again 内部の validation)
• Netscape 4 never 扱うd DateTextBox or TimeOfDayTextBoxes 正確に on the （弁護士の）依頼人 味方する when these 支配（する）／統制するs were in a UserControl or other 指名するing コンテナ. Pages run on NS4 like this would get JavaScript error messages (in the status 妨げる／法廷，弁護士業) instead of 適切に 扱うing keystrokes and reformatting the text.
• Internet Explorer for Mac v5.2.x has been 解放（する）d on Mac OS X. While its earlier 見解／翻訳／版, 5.1 worked 井戸／弁護士席, v5.2 is still a buggy browser. It has no trouble with the JavaScript (no JavaScript errors). However, after all the （弁護士の）依頼人-味方する javascript runs, it hangs when 試みる／企てるing to show the calendar, either in CS_Calendar or when you popup. (最近の IE Mac 見解／翻訳／版s have all struggled with calculating the size of a multinested TABLE. It looks like this is the problem here.) To 解決する this, I've made CS_Calendar become server 味方する only for this browser 見解／翻訳／版. The PopupCalendar is 完全に shut off. Internet Explorer for Mac v5.1 is the recommended IE browser on the Mac for Peter's Date 一括.
• Date 入ること／参加（者） should translate a one segment value ("5") into the day of the 現在の month: 6/5/2003. It was always translating a one segment with the segment that comes first in the ShortDatePattern. In the US, that means it translated to a month instead of a day. Same with two segment 入ること／参加（者）s.
• TimeTextBoxValidator did not （悪事，秘密などを）発見する one 事例／患者 as an error on the server 味方する: when the DateTextBox was blank or 無効の while the TimeOfDayTextBox was filled in, it should 報告（する）／憶測 an error. It did not.
• When using the OnDateChange or OnMonthViewChange events of CSCalendar, its possible to get this runtime error: [ArgumentOutOfRangeException: 明示するd argument was out of the 範囲 of valid values. Parameter 指名する: Year, Month, and Day parameters 述べる an unrepresentable DateTime.]
• When using the OnDateChange event handler of CSCalendar, the event may be 解雇する／砲火／射撃d twice on the page.
• When the TimeOfDayTextBox uses xDateTextBoxControlID, you may get an "多重の 支配（する）／統制するs with the same ID" error when you have placed <DIV> tags around the <FORM> tags.
• Since IE 5.0 has 原因（となる）d more than its 株 of problems with the popupcalendar on DateTextBox, I've 無能にするd it by default on that browser. The TrueBrowser.xSupportsPopupCalendarB 所有物／資産／財産 defaults to 誤った on IE 5.0 for Windows.
• When TrueBrowser.xSupportsPopupCalendarB was 誤った, the DateTextBox still showed the 命令（する） "Calendar" in the 状況 menu.
• The Help button on TimeOfDayTextBox and DurationTextBox appears too far 権利 when arrow buttons are shown on NS7+ and オペラ 7.
• When QuickDateMenu is on a page, it may 生成する a JavaScript error at 負担 time or not popup (if JavaScript errors are turned off) when the browser doesn't support 状況 menus. 特に, the browser 始める，決めるs the TrueBrowser.xSupportsContextMenuB 所有物／資産／財産 to 誤った.

• DateTextBox has a new 所有物／資産／財産, xPopupCalendar.xSharedCalendarDateTextBox. It is an 代案／選択肢 to xPopupCalendar.xSharedCalendarDateTextBoxID to use programmatically when the DateTextBox that you want to 株 is in another NamingContainer.
• When a TimeOfDayTextBox or DurationTextBox shows the arrows and its on 最高の，を越す of another element that is 絶対 positioned, the arrows may ignore clicks on them. This is 予定 to the other element's z-索引, which may be higher than the arrow buttons (which are 絶対 positioned.) This 直す／買収する，八百長をする gives the arrows a z-索引 of 29000.
• v1.1.2 broke the DateTextBoxValidator わずかに. It 報告（する）／憶測s an error when the textbox is blank. Its not supposed to 報告（する）／憶測 an error, letting you （悪事，秘密などを）発見する that 事例／患者 with a RequiredFieldValidator.

• Design change. There is a new validator of DateTextBoxes. DateTextBoxDifferenceValidator calculates the number of days between two DateTextBoxes and compares it to the number of days you 供給する. Use it to 決定する if a 範囲 is within a 最小限 or 最大限 限界. For example, its 無効の if the end date is larger than the start date by 30 days. Or its 無効の if the end date is within 5 days of the start date.
• Design change. DateTextBox has a new 所有物／資産／財産, xReadOnlyAllowsPopupCalendarB. It lets you 始める，決める the textbox to be ReadOnly while the calendar still pops up to edit. If you want to omit using validators, this interface makes the 使用者 select a date from the calendar which is always a valid date. The textbox is 簡単に a 陳列する，発揮する of the value, taking いっそう少なく room on the page than the 伝統的な CS_Calendar.
• When entering a time into a DurationTextBox, if you enter it as a decimal number starting with a period, it reformats to "NaN:NaN". For example, ".2".
• When using xMinDate and xMaxDate on the MonthYearTextBox, 最初 all the months will be enabled when the 現在／一般に selected year has some months outside the min/max date 範囲.
• When you select a date on CS_Calendar, it may show the wrong date in the DateTextBox or upon 地位，任命する 支援する, 報告（する）／憶測 an ArgumentOutOfRangeException with these 条件s: The Today date 独房 is shown on one of the 独房s that are before or after the 見解（をとる）d month. The 使用者 selects that 独房.
• When using CS_Calendar within a UserControl or other 支配（する）／統制する that 器具／実施するs INamingContainer, 地位，任命する 支援する will not retrieve the selecteddate. xSelectedDate will always be 1/1/1.
• When using CS_Calendar, some 所有物／資産／財産 configurations will not 許す xSelectedDate to return the 現在の 選択 on postback. Instead xSelectedDate will return 1/1/1.
• When using TimeOfDayTextBox or DurationTextBox with the hours/minute buttons, they may position incorrectly 最初, 特に on 非，不，無-IE browsers. In 新規加入, when you resize the browser window and the textbox moves, the buttons do not.
• When using the TimeOfDayTextBox or DurationTextBox with a culture that use a period as the time separator (Italy for example), the 命令（する）s to inc/dec the time give the wrong value and the returned time value is incorrect.
• v1.1.1 broke normal use of arrow 重要なs, DEL, Home and END in the DateTextBox. If these 重要なs were not tied to a 命令（する）, they did nothing instead of moving the cursor or 除去するing a character.

• Design change. SpecialDates 支配（する）／統制する has a new 所有物／資産／財産, xPrecedence, which 決定するs what happens when dates overlap. Should the unselectable or selectable date be used?
• Design change. CS_Calendar 支配（する）／統制する has a new 所有物／資産／財産, xAutoPostBackOnSelectionChangeB. When true, any change to the selected date 地位，任命するs 支援する the page. Useful when something else on the page is 関係のある to the selected date.
• Design change. CS_Calendar 支配（する）／統制する has a new 所有物／資産／財産, xAutoPostBackOnMonthViewChangeB. When true, any change to the month 見解（をとる）d 地位，任命するs 支援する the page. Useful when using the SpecialDates 支配（する）／統制する to 許す it to 負担 new dates for the month 見解（をとる）d. (減ずるs the number of dates that you send to the browser.)
• Design change. CS_Calendar 支配（する）／統制する has a new event, OnMonthViewChanged. This event 解雇する／砲火／射撃s when using xAutoPostBackOnMonthViewChangeB and the 使用者 has changed the month. It 供給するs you with the new and previous month selected.
• When entering a date into DateTextBox without date separators, it 適切に reformats the date with separators but いつかs 扱う／治療するs the date like an error was 設立する. Easiest to see when DateTextBox.xErrorAlertOnChangeB is true.
• TimeOfDayTextBox 大（公）使館員d to a DateTextBox subtracts one day from the DateTextBox when the 使用者 uses the Next Hour or minute 命令（する）s and they reach the end of the date. It should 追加する one day.
• An unusual <form> 体制／機構 could 誘発する／引き起こす an error that reads "The Page 欠如（する）s any 支配（する）／統制するs between the <form> tags".
• The Turkish culture code ("tr-TR") 生成するs different lower 事例／患者 text for the HTTP_USER_AGENT which made it not possible to （悪事，秘密などを）発見する the IE browser. Servers running this culture code, and 潜在的に others, make 規模 負かす／撃墜する 支配（する）／統制するs as if its using a Netscape 4 browser.
• オペラ 7 put wide gaps between the arrow buttons of the TimeOfDayTextBox and DurationTextBox 支配（する）／統制するs. (It stretches （米）棚上げする／（英）提議するs to 100% of the page when they don't have a width defined.) 軍隊d a width to position the buttons 適切に.
• TimeOfDayTextBox 最初 may show the wrong international symbol for the AM/PM descriptor when the 現在の thread's descriptor is different from what you manually 割り当てる to TimeOfDayTextBox.xDateTimeFormatInfo.AMDescriptor.
• TimeOfDayTextBox doesn't 扱う the AM/PM designator of Spanish speaking cultures 適切に. It 報告（する）／憶測s validation errors and 始める，決めるs the 最大限 number of characters too small. The Spanish AM/PM designator 含むs periods and is more than 2 characters. Both were 問題／発行するs that are now 解決するd.
• In cultures that use a 24 hour clock, their DateTimeFormatInfo.AMDescriptor and PMDescriptor may be blank. This 混乱させるs the TimeOfDayValidator. It will 原因（となる） a time between 0 and 11:59 to 追加する 12 hours.
• When using the xSharedCalendarDateTextBoxID 所有物／資産／財産 on the DateTextBox, the keystroke and 状況 menu 命令（する） to popup the calendar doesn't work. It may 報告（する）／憶測 a JavaScript error if selected.
• The TimeTextBoxCompareValidator いつかs 報告（する）／憶測d an error when the 条件s were valid with （弁護士の）依頼人-味方する validation. 要求するs that the TimeOfDayTextBox is connected to DateTextBoxes.

• The License とじ込み／提出する path can be overridden with either of these web.config とじ込み／提出する せいにするs: PPP_LicenseVirtualPath or PPP_LicenseFilePath.
• The Submitted event has its arguments 拡大するd to 含む the 記録，記録的な／記録する ID of the selected answer when the 使用者 投票（する）s in the field fAnswerID.

• Design change. When the 使用者 changes the date in CS_Calendar and it updates the DateTextBox, 焦点（を合わせる） is returned to the textbox.
• When the DateTextBox shows an error with a fore or 支援する color and you 攻撃する，衝突する the Today or Special 命令（する）s, it should 逆戻りする 支援する to the 初めの field colors.
• When using DateTextBox.xAutoPostBackB, 地位，任命する 支援する does not happen when the change comes from the popup calendar.
• The QuickDateMenu 扱うs 親族 dates whose PeriodType is ４半期/4分の1 incorrectly. Some dates are incorrect. When Today is in December, is throws an exception.
• When using xMinDate or xMaxDate on CS_Calendar and CS_Calendar uses a server 味方する interface, 底（に届く） 国境s are 行方不明の on some day 独房s that are outside the 範囲.
• When CS_Calendar.xTodaysDate is 割り当てるd, it is ignored when the calendar is drawn in design 方式 and in server 味方する 方式. It kept using DateTime.Today.
• The CSC_GetDay JavaScript 機能（する）／行事, 利用できる for 使用者s programming, had a bug where it returned the month instead of the day.
• オペラ 7 報告（する）／憶測d a JavaScript error when there was a CS_Calendar (含むing within a DateTextBox) without any Help buttons. The 状況 menu code initialization ran. オペラ 7 doesn't support the 権利 click 状況 menu. So the variables were not initialized in オペラ 7.
• When CS_Calendar.xSpecialDate is 割り当てるd, its style sheet (xSpecialCssClass) is ignored when the calendar is drawn in design 方式 and in server 味方する 方式.
• When CS_Calendar has xMinDate 始める，決める to the first date of a month or xMaxDate to the last date of a month, the movement 命令（する）s will 許す going one month beyond the 限界s.
• 予定 to a bug in the JavaScript compression program, DateTextBox.js was not fully compressed. It is now 6K smaller.

• Use a DataGrid to 含む／封じ込める an EditItemTemplate with a DateTextBox. With SmartNavigation on, the popup calendar looks 罰金. But the PopupMonthYearPicker and ContextMenu within the calendar draw transparently making the calender see-through.
• 追加する a DateTextBox to an 絶対 positioned （米）棚上げする／（英）提議する that has a 非，不，無-無 Left or 最高の，を越す position. Have a dropdownlist or listbox below it. 権利 click on the DateTextBox to get its 状況 menu. Looks 罰金. Popup the calendar and it will be 部分的に／不公平に overwritten by the SELECT element. Refresh the page and open the calendar first. It will be 罰金 but the DTB 状況 Menu will now have a problem with the SELECT element. This is その上の work started in v1.0.1.
• IE Mac 5.1 now 扱うs the popup calendar's position 正確に when it is 含む／封じ込めるd within a （米）棚上げする／（英）提議する. This is a workaround to a bug in that browser. However, IE Mac 5.0 still positions incorrectly. (The same 直す／買収する，八百長をする really exposes some bugs in that browser's ability to position and size DIV tags.)
• IE Mac positioned the QuickDateMenu incorrectly when 含む／封じ込めるd within a （米）棚上げする／（英）提議する. (This 直す／買収する，八百長をする is very different from the one above.)
• Design change. You can 供給する an 代案／選択肢 path to the Licenses folder and the scripts folder with an 入ること／参加（者） into Web.Config. See the documentation.
• If you had the DateTextBox 明白な but on a 地位，任命する 支援する hid it 経由で its 明白な 所有物／資産／財産 or that of a parent 支配（する）／統制する, the DateTextBox wouldn't 保存する the value entered when it was a new page.
• If any popup 支配（する）／統制する is 含む／封じ込めるd within a <DIV> with the 洪水 style 始める，決める to show scrollbars, when the 地域 is scrolled, clicking on a 独房 often の近くにs the popup without taking the 推定する／予想するd 活動／戦闘. For example, the PopupCalendar will の近くに without selecting the date you clicked on.

• New feature. CS_Calendar now supports changing the first day of the week with the xFirstDayOfWeek 所有物／資産／財産.
• Now supports オペラ v7.0 Beta 1. It's almost a 十分な 実施 of features (much better than previous オペラ 見解／翻訳／版s.) See documentation for 制限s.
• QuickDateMenu now becomes invisible with the DateTextBox to which its 大（公）使館員d is also invisible.
• CS_Calendar drew the 底（に届く） 国境 around the 最高の，を越す 列／漕ぐ／騒動 of days in the previous month with the "OtherMonthBorderColor". It now draws that 国境 with the 現在の month 国境 color.
• The popups (calendar, monthyearpicker, 状況 menu) will appear behind nearby 減少（する） 負かす／撃墜する 名簿（に載せる）／表（にあげる）s and listboxes on IE/勝利，勝つ browsers. IE 5+ has a design where it does not 許す 絶対 positioned above these fields. See http://support.microsoft.com/default.aspx?scid=KB;en-us;q177378
  This 直す／買収する，八百長をする 作品 in IE 5.5+, 偉業／利用するing a design change with IFrames that was introduced in that 見解／翻訳／版. IE 5.0 remains 不変の.
• The popups (calendar, monthyearpicker, 状況 menu) may appear behind other 絶対 positioned 支配（する）／統制するs whose Z-索引 is greater than 2000. Updated these 支配（する）／統制するs to have a Z-索引 starting at 30000 and updated the Troubleshooting section of the docs to 解決する this when 使用者s have Z-索引s greater than 30000.
• The popup calendar does not position 正確に when inside an 絶対 positioned DIV, such as the FlowLayoutPanel. Positioning code 直す／買収する，八百長をするd.
• The validators would not show up when positioned before the DateTextBox on the page.
• The DateTextBox 所有物／資産／財産 xToolTipInStatusB doesn't work. It 原因（となる）s a JavaScript error 予定 to a carriage return in the tooltip. It never 割り当てるs a valid tooltip to the status line.
• After getting a validation error, a DateTextBox with xErrorBackColor or xErrorForeColor 所有物／資産／財産s 始める，決める will 保持する those colors when the 使用者 （疑いを）晴らすs the field and makes the field lose 焦点（を合わせる）. The field is valid when its blank and should 回復する itself to 非，不，無-error colors.
• On IE 5+ browsers, if you open a 状況 menu or the popup calendar associated with the DateTextBox, then click in the textbox to の近くに those 反対するs, any typing in the textbox will be unfiltered (appears to be a bug in IE.) 直す／買収する，八百長をする 始める，決めるs 焦点（を合わせる） during an onclick event.
• If the popup calendar is 含む／封じ込めるd within a hidden parent when the page is first 負担d (hidden by the style "陳列する，発揮する=非，不，無"), its （米）棚上げする／（英）提議するs will be misaligned. The （米）棚上げする／（英）提議する width 計算／見積りs run during page initialization but the 陳列する，発揮する=非，不，無 style gives it 無s for 現在の widths. That makes it impossible to calculate the widths. In this 事例／患者, it 延期するs calculating the widths until the first time it pops up (which 課すs a slight 延期する on the first popup but only in this 事例／患者.)
• If you manually 始める，決める xTrueBrowser.xSupportsCalendarB to 誤った, the CS_Calendar will still show the PopupMonthYearPicker. When the 使用者 clicks, it won't popup (giving a JavaScript error if errors are on). The popup is dependant on the CSCalendar.js とじ込み／提出する 存在 負担d which its not in this 事例／患者. The 直す／買収する，八百長をする hides the MonthYearPicker and 状況 menu (as it too 要求するs the CS_Calendar とじ込み／提出する.)
• CS_Calendar. When the WeekRows （米）棚上げする／（英）提議する 欠如（する）s an outer 国境 but has 国境s around each day and the CellSpacing is 0, some 国境s are 行方不明の on day 独房s that are along the outer でっちあげる，人を罪に陥れる. 影響する／感情s design 方式 and server-味方する CS_Calendar 方式.
• If you use the @Page Culture 所有物／資産／財産, it does not 影響する／感情 the xDateTimeFormatInfo 所有物／資産／財産 on any of the 支配（する）／統制するs. The ASP.NET engine initializes the 所有物／資産／財産 after my 支配（する）／統制するs do. My 支配（する）／統制するs now 延期する their initialization to support the Culture 所有物／資産／財産.