I am writing a dll to handle error reporting and some other functionality.
This dll is indended to be shared across several different web sites and some non web stuff like console apps. This dll will be referenced by all our projects.
What is usually the standard way of doing configuration stuff on a dll. For example depending on what server the application is on settings like what mail server to use and what email address to send to might be different.
Having the app pass the settings by creating a new instance seems like it's not the ideal way of doing it.
Can a dll detect if it is being used by an ASP.Net app vs a console app and call the correct configuration file? Should I put the information in the registry?
Thanks
This dll is indended to be shared across several different web sites and some non web stuff like console apps. This dll will be referenced by all our projects.
What is usually the standard way of doing configuration stuff on a dll. For example depending on what server the application is on settings like what mail server to use and what email address to send to might be different.
Having the app pass the settings by creating a new instance seems like it's not the ideal way of doing it.
Can a dll detect if it is being used by an ASP.Net app vs a console app and call the correct configuration file? Should I put the information in the registry?
Thanks