G
Guest
Let's say I create a class that I want to use in lots of different contexts
(e.g. as a .CS file put in the CODE folder in an ASP.NET2 application, in a
WindowsForms application, in a Console application). And let's say that I
want to be able to store certain configuration information externally. My
question is, short of just creating my own XML settings file that I read in
the class, is there a mrecommended way of storing and accessing this
information across all of these uses?
See, in a WindowsForms application, I can use a Resource, in an ASP.NET
application, I can pull app data out of Web.Config AppSettings, etc. But is
there a unified approach I can take instead?
Alex
(e.g. as a .CS file put in the CODE folder in an ASP.NET2 application, in a
WindowsForms application, in a Console application). And let's say that I
want to be able to store certain configuration information externally. My
question is, short of just creating my own XML settings file that I read in
the class, is there a mrecommended way of storing and accessing this
information across all of these uses?
See, in a WindowsForms application, I can use a Resource, in an ASP.NET
application, I can pull app data out of Web.Config AppSettings, etc. But is
there a unified approach I can take instead?
Alex