# Configuring custom web forms to work with previous versions of WorkflowGen.My (2.x) in v6 or v7

**URL:** https://discuss.workflowgen.com/t/configuring-custom-web-forms-to-work-with-previous-versions-of-workflowgen-my-2-x-in-v6-or-v7/226
**Category:** Visual Studio Web Forms
**Created:** [January 19, 2016, 9:05am UTC](https://discuss.workflowgen.com/t/configuring-custom-web-forms-to-work-with-previous-versions-of-workflowgen-my-2-x-in-v6-or-v7/226 "2016-01-19T09:05:27Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)
#### Post date: [January 19, 2016, 9:05am UTC](https://discuss.workflowgen.com/t/configuring-custom-web-forms-to-work-with-previous-versions-of-workflowgen-my-2-x-in-v6-or-v7/226/1 "2016-01-19T09:05:27Z")

</div>

If you are using custom web forms configured in .NET 2.0, you can keep using them in .NET 2.0 or migrate them to .NET 4.

**To configure custom web forms for .NET 2.0:**

1. Use `WorkflowGen.My.dll` in version 2.x.

2. Use a .NET 2.0 application pool.

3. Disable **Web apps secure mode** in the **Security** section on the **General** tab in the **Configuration Panel**.

4. Define or update the following nodes in the web forms’s `web.config` file:

5. If your web form’s authentication is configured to use the built-in WorkflowGen authentication mode, then the new password hashing mode (One-way Hashing) introduced in version 6.1 will not be compatible with your web form. There are two solutions: