Instantiating and Managing Custom C# Form Classes

Create, open, and control multiple forms in structured OOP style

As your applications grow, you’ll likely need more than one form — for example, a login screen, a settings window, or a results viewer. Rather than cramming everything into one file, you can build a better UI architecture by creating custom form classes.

In OOP, forms are just classes that inherit from Form. That means you can create, pass data between, and control them like any other object.

🧱 Defining Your Own Form Class

To create a new form:

🛠 In Visual Studio:

• Right-click your project → Add → Windows Form → Name it FormSettings.cs
• Visual Studio will generate:
  • FormSettings.cs
  • FormSettings.Designer.cs
  • Partial class FormSettings that inherits from Form

🧪 Example: Basic Custom Form

// FormSettings.cs
public partial class FormSettings : Form
{
    public FormSettings()
    {
        InitializeComponent();
    }
}

✅ Now you have a standalone form class that can be used from other parts of your application.

🧰 Instantiating a Custom Form

From another form (like MainForm), you can create and show FormSettings:

🔹 Modal Form (Blocks until closed)

FormSettings settingsForm = new FormSettings();
settingsForm.ShowDialog();  // Use for dialogs and user input

🔹 Modeless Form (Stays open independently)

FormSettings settingsForm = new FormSettings();
settingsForm.Show();  // Use for tools, dashboards, etc.

🔄 Passing Data to Forms (Constructor Injection)

// In FormSettings.cs
public FormSettings(string username)
{
    InitializeComponent();
    lblUser.Text = $"Welcome, {username}!";
}

// In MainForm.cs
FormSettings settings = new FormSettings("Alice");
settings.Show();

✅ This is classic OOP dependency injection — you’re giving the form the info it needs via its constructor.

📬 Getting Data Back From a Form

For modal forms (like input dialogs), you can define public properties to expose selected values:

// In FormSettings.cs
public string SelectedTheme { get; private set; }

private void btnApply_Click(object sender, EventArgs e)
{
    SelectedTheme = cboTheme.SelectedItem.ToString();
    this.DialogResult = DialogResult.OK;
    this.Close();
}

// In MainForm.cs
FormSettings fs = new FormSettings();
if (fs.ShowDialog() == DialogResult.OK)
{
    string theme = fs.SelectedTheme;
}

🔁 Reusing Form Instances (Advanced)

You can create a singleton-style form or store form instances for reuse:

private FormSettings _settingsForm;

private void ShowSettings()
{
    if (_settingsForm == null || _settingsForm.IsDisposed)
        _settingsForm = new FormSettings();

    _settingsForm.Show();
    _settingsForm.BringToFront();
}

📚 Summary

✅ Best Practices

• ✅ Give each form its own class (separation of concerns)
• ✅ Use constructor injection for required inputs
• ✅ Use public properties or events to return values
• ✅ Avoid keeping too many forms open at once
• ✅ Clean up form instances using .Dispose() or .IsDisposed

🧪 Quick Challenge

1. Create a new form class FormAbout with a label and a Close button.
2. In MainForm, add a button to show the About form using ShowDialog()
3. Try passing the application version into the constructor and displaying it

💬 Want to build a form navigation system, or explore passing objects between forms (like user profiles or models)? Let us know!