App design help with Resources/Sat Assem.
Here is current situation... .Net 1.1, I have an Asp.net and WebService front end applications that sit on top of our .Net "business" layer. All of these apps are seperate projects in our solution. I need to implement multiple language capabilities. I already set the culture info in the web layer so numbers/dates are formatted correctly. However now I need the ability to change label values and error messgages. I've seen how I can do that in the Web application by just adding multiple resource files and it embeds them etc.. but my problem is that when I throw an error from my business layer I need the ability to change those error messges as well...So should I have a seperate application with only resource files in it and then link it to our web application AND our business application? Or in our business layer do I always assume that it's always being called (it probably always will be) by the web UI or the webservice?...then I can create a resource manager in the business layer and hand it the "calling assembly" to get a reference to the resource object(s)...
I'm hesitant on making the resources a seperate application because we have alot of clients and it would seem like it would be a support nightmare to make sure that everything got linked properly...currently we just use the build process to make an MSI and most everything is done. However if we're painting ourselves into a corner by having the resources part of the web app(s) then that may override any inconveniance of having to other steps to link them...
Thanks
Doug