<p>I have an offline paper based form. I need to convert it into a software that people can use on their computers to fill and submit information. Since the form (it is a tax return) requires considerable time in filling, it is not convenient to have it online. I would much rather have a simple exe which gathers information, applies validation rules and then uploads a structured data file (like an XML file) containing the filled info.</p>

<hr>

<p>I mean that I have an offline paper based form. I need to convert it into a software that people can use on their computers to fill and submit information. Since the form (it is a tax return) requires considerable time in filling, it is not convenient to have it online only. I would much rather have a simple exe which gathers information, applies validation rules and then uploads a structured data file (like an XML file) containing the filled info.</p>

What do you mean, exactly? When you build a project containing a form, it will already build an executable if the project type is "Windows Forms Application".
If you've got one project with several forms and you need one executable per form, you should split your project out - one project per form. (You
could
make the code display a different form based on executable name - or have several entry points and build the same code with different
```
/main
```
flags, but that would be pretty nasty.)