> For the complete documentation index, see [llms.txt](https://docs.workflowgen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workflowgen.com/vs-web-forms/requirements.md).

# Requirements

## Technical requirements

* WorkflowGen 7 or later<br>
* WorkflowGen.My 4.x<br>
* .NET Framework 4.6.1 (.NET Framework and ASP.NET 4.7.2 are supported for runtime and web form development)

## WorkflowGen.My assembly <a href="#workflowgen-my-assembly" id="workflowgen-my-assembly"></a>

In order to implement a web form, you must have WorkflowGen.My referenced in your project. Follow these instructions to directly reference an assembly in your web project:

1. Create a `\bin` directory under your website's root folder (e.g.`\wfgen\wfapps\webforms\MyWebForm\bin`).<br>
2. Copy the `WorkflowGen.My.dll` file to this folder.<br>
3. Right-click on your project name and choose **Add reference...** <br>
4. Click **Browse**.<br>
5. Navigate to the `\bin` directory you just created and choose the `WorkflowGen.My.dll` file, then click **OK**.

WorkflowGen.My is now referenced in your project.

## Web configuration <a href="#web-config" id="web-config"></a>

`WorkflowPage` does not use any particular `web.config` settings.

## XML form data

The form data is the XML file used to store all your web form data. A file type data element called `FORM_DATA` should be created and left empty.

## Files and folders

Your CSS styles should be located in a sub-directory called `\css`, and your form archive style sheet file should be called `form_archive.css` because `WorkflowPage` will look for this particular file in this location to find it.

If you don't want to use these default values, you can always change the `FormArchiveCssPath` property, whose default value is `\css\form_archive.css`.

A form archive file called `form_archive.htm` will be created by default, but you can use any name you want by changing the value of the `FormArchiveFileName` property.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.workflowgen.com/vs-web-forms/requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
