What's the best way for a common library to know what context - a.k.a. the calling app - it is in? I'm in a very controlled enterprise environment... is there a better way for the library to know what application it is getting called from than reading a setting in the config file? What do you use for this type of thing? //the rest of th...
Here's the situation: we have a common library which can retrieve database connection details from a central configuration store that we have setup. Each application uses this library when working with a database. Basically, it will call a stored procedure and say "I am {xyz} application, I need to connect o " and it will return the co...
Here is the setup: We have a common library that I've developed that is used by all developers on any new applications or more than trivial changes to old applications. When we make a change, we up the minor version number (2.0 to 2.1) if the API is not broken, but if we break the API then we up the major version number...
I've got a common library that contains enums that are shared between a WCF Service and a client by means of the DLL. Yes, I know the better way of doing this is to create a service out of my common lib - that's for later. I've made a change to my common lib, adding another field to the enum. After compiling, I've updated the DLL's in...
My team and I are working on several projects that collectively depend on some common libraries. These common libraries are currently checked out together with the projects, using svn:externals. The question is, should the projects' trunks track the HEAD of each library, or be linked to specific revisions? The issue libraries are very ...