This might not be right, but if "the same files [loaded] from different locations" are in fact identical, couldn't you let the CLR know that by signing the file before making copies? It should know that two files that have the same name and signature are the same file even though they loaded from different paths.
At 03:33 PM 2/27/2007, Dean Cleaver wrote >Hi, > >I've been using Remoting on several projects with great success for >several years now, however I've now struck a hurdle - one of my projects >is an Outlook Addin, and it also loads as OCX controls into HTML pages >in Outlook folders - these are each in separate AppDomains over which I >have no control, and one uses shadow copy one doesn't, so they load the >same files from different locations. This causes remoting to complain >that it can't cast A to A, because it thinks they're different. Putting >them in the GAC isn't really an option either, as this system is >auto-updated over the web while running as a user. Otherwise, the GAC >might have solved the problem. > >The obvious choice is WebServices, but some projects have 150+ classes >in them that I call - I'd have to make 150+ web services, but also I'd >have to add 150+ web references to the Business Services project - seems >very messy to me. > >Another option is to create one massive web service with functions like >Aload, ASave and BLoad etc that call the existing Data Access class >functions, and return the same objects/values. Seems like it would get >out of hand quickly - 150+ classes with 10+ methods each - that's a lot >of functions in one web service. > >Are there any other options I have missed? > >Dino J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
