You said you have multiple solutions with multiple projects; here is the most likely scenario,
Solution 1 has Project 1 and Project 2 Both Referencing IDBAdapter but Possibly Different assemblies Solution 2 Has Project 3 Referencing Project 1 and Project 2 Her is what happens when you build it Project 1 and Project 2 Both Get Built without any problems since they each have there own Bin Directories the (Possibly) Different IDBAdapter Assemblies have no affect, now Project 3 is built for this to happen all referenced assemblies with their dependencies are copied to the local directory this means Project 1 with its version of IDBAdapter And Project 2 with its version of IDBAdapter, here is where the problem occurs, since both assemblies have the same filename but different version the newest version will be copied to the directory leaving one of the two projects without its version of IDBAdapter I have run into this same problem a few times, (Solutions With up to 30+ Projects with Many co dependencies etc) The best way to fix this is to start by removing all references IDBAdapter in all your projects, then do a search of your drive for any copies of IDBAdapter.dll, delete all but the one you want to use, Add the reference back and build your Solutions. This will sometimes cause a build failure on your first attempt since the dependencies might be perceived as missing, if this happens just click on build a second time I Hope this helps Paul Stevens Senior Developer Resolution Software -----Original Message----- From: Loc Nguyen [mailto:[EMAIL PROTECTED]] Sent: 06 June 2002 09:04 PM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] VS.Net "Copy Local" feature Hmm... I remember someone from MS mentioning something about the assembly version number. I do not remember what it was he said about it. However, in my second posting to this issue, I mentioned that I did a grep on *.* at the root of our source tree for the offending version number string and could not find any file with this string. In addition, I only have exactly one copy of the offending assembly on my system. It is the newer version. Therefore, I believe VS.Net is caching the old version number somewhere. This issue is hugely hindering productivity. MS is up to their old automagic crap (e.g. IE security settings, cross scripting, COM integration in outlook). Has anyone at MS heard of the KISS rule of thumb? You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
