A
avinashraj
Hello,
In the past when working with VB.net, if several projects needed to use
the same set of constants, I would declare them in a Class file and
share the class file (in VSS) b/w several projects.This way, if one of
the projects updated the file, it impacted the other projects aswell.
Typically the constants were col names used in data tables etc...
This worked well because VB.net did not have explicit name space
declaration and any class would belong withn the root name space.
I am now working on a C# solution and was trying the same technique
out. I cant do it because each class needs explicit name space
declaration. I know this can be put within some kind of a resource
assembly and be re used. But case in point I want to keep some of the
assemblies as light and independant as possible and want to avoid any
such references.
Is there another way this can we worked out ? Any ideas will be great
Regards,
Avinash
In the past when working with VB.net, if several projects needed to use
the same set of constants, I would declare them in a Class file and
share the class file (in VSS) b/w several projects.This way, if one of
the projects updated the file, it impacted the other projects aswell.
Typically the constants were col names used in data tables etc...
This worked well because VB.net did not have explicit name space
declaration and any class would belong withn the root name space.
I am now working on a C# solution and was trying the same technique
out. I cant do it because each class needs explicit name space
declaration. I know this can be put within some kind of a resource
assembly and be re used. But case in point I want to keep some of the
assemblies as light and independant as possible and want to avoid any
such references.
Is there another way this can we worked out ? Any ideas will be great
Regards,
Avinash