C#

private void Form1_Load(object sender, EventArgs e)
 {
     List("Select * from Win32_BIOS");
 }

 private void List(string query)
 {
     ManagementObjectSearcher m = new ManagementObjectSearcher();
     m.Query = new ObjectQuery(query);
     foreach (ManagementObject mo in m.Get())
     {
         foreach (PropertyData pd in mo.Properties)
         {
             if (mo[pd.Name] != null)
             {
                 if (mo[pd.Name] is string[])
                 {
                     foreach (string s in (string[])mo[pd.Name])
                     {
                         MessageBox.Show(s);
                     }
                 }
                 else
                 {
                     MessageBox.Show(pd.Name + ":" + mo[pd.Name].ToString());
                 }
             }
         }
     }
 }

"Find out what you have to do before deciding on the language to use"

NextDouble()      // will return a random number between 0.0 and 1.0<br />

Random rnd = new Random();
int a = rnd.Next(10);
int b = rng.Next(10);

saxisa wrote:

Is there a good reason to have so many statics?

saxisa wrote:

How can I refactor or manage this code?

saxisa wrote:

There are 180,000 lines of code, and only 2 namespaces encompasing all of it. Shouldn't namespaces be used similar to packages in java?

Christian Graus wrote:

It's just an idiom. I prefer to write static classes, but a class with a static Instance property works just as well. What is the difference ? If a class does not have state, then static makes sense to me.