# Release Notes

## 6.0.2

Major change on tool version due to visual modifications and equity with WebMap tools.

* New UI logos to refer WebMap for WebForms conversions
* Improvements on the shared components

## 2.0.0 - Beta version

Component's version for this release:

* *WebForms Components version 2.0.14*
* *WebForms BundleBasic version 1.10.6*
* *WFNet DCP version 9.13.1*
* *WFNetKendoComponents version 8.3.3*

### Added

* **Upgrade to use Angular 13 packages for target applications, this due to the long-term support of Angular versions for the converted applications.**
* Assessment improvements for accurate process of evaluation, add stub filtering new rules to evaluate more nodes of the source code than ASP and been able to read more nodes information.
* Add new value in assessment Status column report output, value 2 means HTML elements that were not mapped and that code will be part of the output as it is in source code.
* **Net 6 update to add support a new framework and it is in a long-term support, due to the current support for .Net 5 is over.**
* Added mapping of the rangevalidator control.
* Added implementation of the range validator.
* Added support to configure SortingActionService for WebForms.
* Add entity framework reference.

### Fixes

* Remove dependency in Kendo Editor, to fix npm installation issues and stabilize RichTextBox basic implementation.
* Fixed image and hyperlink controls.

### 1.2.0 - Beta version

*Component’s version for this release:*

* M*obilize.Web.BundleBasic.All: 9.12.4*
* *Mobilize.Web.BundleBasic.WebForms.All: 1.10.4*
* *Winforms-components: 7.54.9*
* *Webforms-components: 1.27.12*

#### Added

* Assessment improvements for accurate process of evaluation, add stub filtering new rules to evaluate more nodes of the source code than ASP and been able to read more nodes information.
* Add new value in assessment Status column report output, value 2 means HTML elements that were not mapped and that code will be part of the output as it is in source code.
* Net 6 update to add support a new framework and it is in a long-term support, due to the current support for .Net 5 is over.
* Added mapping and implementation of range validator control.
* Added support to configure SortingActionService for WebForms.
* Entity Framework references supported.

#### Fixed

* Remove dependency in Kendo Editor, to fix npm installation issues and stabilize RichTextBox basic implementation.
* Fixed image and hyperlink controls behavior.

### 🎉Initial release! 

* WebForms conversion UI
* Implemented features: 
  * [Master Pages support](/webmap/webforms/desktop-compatibility-platform-dcp/pages-and-master-pages.md)
  * [Controls implementation](https://docs.gapvelocity.ai/webmap/webforms/pages/1zAhXP1W16w1fVkFbMdr#mobilize.web.bundlebasic.webforms)
  * [Control initialization mechanism ](/webmap/webforms/designer-classes-on-webforms-conversion-tool.md)
  * Data Synchronization
    * [Controls](https://docs.gapvelocity.ai/webmap/webforms/pages/1zAhXP1W16w1fVkFbMdr#mobilize.web.bundlebasic.webforms.dto)
    * [Bulk data handling ](/webmap/webforms/desktop-compatibility-platform-dcp/gridview-and-datalist-data-synchronization.md)
  * [Support for Response / Redirect objects](/webmap/webforms/desktop-compatibility-platform-dcp/http-objects.md)
  * Cookies authentication support
* Supported files:
  * Back-end code classes \*.**cs** 
  * ASP HTML files \*.**aspx**
  * ASP Back-end classes **\*.apsx.cs**
  * ASP User Control file **\*.ascx**
  * ASP User Control Back-end classes **\*.ascx.cs**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gapvelocity.ai/webmap/webforms/release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.