One static and one normal class share the same configuration?

Question

I have a configuration class that is shared in my project:

public class BarcodeConfig
{
    public string LotStandardDigits { get; set; }
    public string LotOldStandardDigits { get; set; }
    public int LotOldNumofDigits { get; set; }
    public int LotStandardNumofDigits { get; set; }
}

In my main class implementation i have 2 classes. One static (for utilities and the other that contains all my intended logic:

public static class BarcodeUtil
{
...
}

public class BarcodeBLL
{
...        
}

I want to be able to use the same configuration class for both my static and normal class. Is it best to make the config class static? or not?

score 4 · Accepted Answer · answered Dec 14 '12 at 11:31

4

I prefer instantiating config object. In case of those static methods I'd pass the config as an argument to each of this utlility methods separately.

This allows to use utility methods for completely different purposes by completely different modules at the same time and makes them more elastic.

answered Dec 14 '12 at 11:31

Grzegorz Sławecki

1,587
13
26

Ok using OOP operations on my config class seems right. Passing the config each time to my util methods feels also right becasue i make target different domain each time. For my normal class should i just pass the object in the constructor then? – e4rthdog Dec 14 '12 at 11:41
Agree. But don't pass entire config object, only values which are needed for helper method you want to call. – Alexander Bortnik Dec 14 '12 at 11:42
Agree. Static utility class means stateless. – Sergio Rykov Dec 14 '12 at 11:44
@ValtasarIII: And how to do that? you mean to just pass the fields separately? – e4rthdog Dec 14 '12 at 12:01
@e4rthdog Yes, for normal class passing in constructor is ok for me. Doing this You bind your instance with a config instance which is the idea i like. – Grzegorz Sławecki Dec 14 '12 at 12:18
@e4rthdog Yes, pass them separately. – Alexander Bortnik Dec 14 '12 at 13:13

score 0 · Answer 2 · edited May 23 '17 at 11:55

0

If you use unit tests it's better not to have static classes, because it's much harder to fake them. This is an interesting discussing:

When to use static vs instantiated classes

edited May 23 '17 at 11:55

Community

1
1

answered Dec 14 '12 at 11:28

Rui Jarimba

9,732
10
46
74

@e4rthdog: Edited my answer, see the link. – Rui Jarimba Dec 14 '12 at 11:31

One static and one normal class share the same configuration?

2 Answers2