Background: I have an ASP.NET dll which I'm referencing from a classic ASP web application. [Pause for groaning.] I've added the dll to the GAC and registered it with regasm and so forth, per various articles here at SO and elsewhere. It all works: the object is created, a database is called, everything ends well.
The problem, though, is that when I go to make a simple Settings.Settings configuration change on the fly in production (by editing AppName.dll.config) the change doesn't "take." I tried unregistering; even restarting IIS. The config value won't budge. Am I editing the correct file? Do I need to recompile? (That would seem to defeat the purpose of the .config file, but...)
Thoughts? Is this an oddity arising from the not-ideal ASP/ASP.NET mixture?
Thanks.