How to bring a value from a class?

[aeris]

hello, sorry to bothering all.

May I know what is the coding to bring a value from a class's constructor?

Below is the class.

public class ABC
    {
        public String aa;
        public String bb;
        public Int32 cc;
 
        public ABC(String Aa, String Bb, Int32 Cc)
        {
            this.aa = Aa;
            this.bb = Bb;
            this.cc = Cc;
         }
    }  

Let's say i wan bring the value of ABC.bb from the class to a window form. How to pass the value from the class??

Please help. Thanks in advance. :)
By, Aeris.

[tlhintoq]

The form would reference the instance of the class.

ABC myNewABC = new ABC("Alpha", "Bravo", "Charlie")

you would then reference it through the new instance

myNewABC.aa

[aeris]

Thanks for the reply.

But I actually having two forms.

From the first form, let's say I had reference the instance,
ABC myNewABC = new ABC("Alpha", "Bravo", "Charlie")

The Alpha, bravo and charlie are been inserted into the class.

And then, how to pass the value from the class to the Second Form?

[aeris]

@tlhintoq
Thanks for the reply.

But I actually having two forms.

From the first form, let's say I had reference the instance,
ABC myNewABC = new ABC("Alpha", "Bravo", "Charlie")

The Alpha, bravo and charlie are been inserted into the class.

And then, how to pass the value from the class to the Second Form?

[tlhintoq]

How do I get my Form2 to react to something on my Form1?
How do I make my Form1 control something on my Form2?

Although you can have Form1 directly access items on Form2 it isn't the recommended way to go. It ties the two forms tightly to each other. If a change is made in Form2 such as removing one of the controls, then code in Form1 breaks.
It is better to Form1 raise an event, and have Form2 contain its own code for how to react to this. This places responsibility for Form2 within Form2, and Form1 within Form1.
It keeps Form1 blissfully ignorant of Form2 - and a logging component - and a progress component, and a dozen other little black boxes that can be subscribed to events in Form1, all without Form1 being made responsible for directly affecting controls other than itself.
Events tutorial (including Form to Form which is the same as class to class)
This tutorial for a cash register does exactly that: It makes a virtual numeric keyboard.
Bad: Directly accessing controls of one class/form from another.

bool IsOn = Form2.button1.IsChecked;

Good: Use a property to get such information

//Form1
bool IsOn = Form2.IsOn;

//Form 2
public bool IsOn
{
   get { return button1.Checked; }
   set { button1.Checked = value; }
}

It's a subtle but important difference as your applications become more complex. Using properties means your target class/form (Form2) can be changed and updated a thousand different ways yet won't negatively impact the classes that are reading from it. If you change the name of a control for example: No break in all your other classes. If your target form evolves where it needs to do 10 things when it is turned on, then the responsibility stays within Form2, and that burden on not put on Form1 and a dozen other forms that might be using Form2. The goal is to compartimentalize the work so that Form2 is responsiblity SOLELY for Form2. From1 should only have to say "Turn on" or "Turn Off"

Form2
public bool IsOn
{
   get { return btnMeaningfulName.Checked; }
   set {
            btnMeaningfulName.Checked = value;
            panelDashboard.Visible = value;
            labelStatus = value == true ? "On" : "Off";
            btnRunNow.Enabled = value;
}