Hi all,

I have a solution that contains a windows application project with forms. Also, the solution has a dll which contains forms and is instatiated by the main windows project. That part works fine and the forms in the dll come up without any problems.

I'm getting myself a little confused on how I should setup global variables to be used between both project files.

My thoughts now is to create a GlobalVars dll that would be referenced in both project files.

Does this sound like a good idea or is there a better way to do it?

Thanks,

Fishy.

A global vars dll sounds ok: it makes sure you don't get cyclic references in your projects. Make sure you export readonly statics, not const statics.

Otis wrote:

Make sure you export readonly statics, not const statics.

Excuse my ignorance , but what do you mean by that?

Thanks,

Fishy

Fishy wrote:

Otis wrote:

Make sure you export readonly statics, not const statics.

Excuse my ignorance , but what do you mean by that?

Thanks,

Fishy

If you do:

public const string Foo = "lala";

in assembly A and you use Foo in assembly B, the actual value 'lala' is compiled in assembly B. This means that if you change A, B will still use 'lala'.

if you do:

public static readonly string Foo = "lala";

for B it won't make a difference, but now, a reference to A.Foo is compiled, not 'lala'. This means that if A changes, B will pick up the change.

ahh, ok, that makes sense.

Thanks again for your quick response

in assembly A and you use Foo in assembly B, the actual value 'lala' is compiled in assembly B. This means that if you change A, B will still use 'lala'.

Facinating. I didn't know that. I'm guessing that knowledge was learned in a very difficult and painful debugging session.

Heh, luckily I read it somewhere and every time I type in 'const' I remember it and replace it with 'readonly...'. It's the answer to the common question: "Why is there 'readonly' in C# while there's also const?