I thought this may be interesting to the folks over ehre. One of the products I work on needs the Web Services Enhancements package from MS. In one of our packages we ship the WebServices DLL(Microsoft.Web.Service2.DLL) along with our product. For some reason I had compiled the package with version 2.0.0.0 of the Microsoft DLL but during packaging grabbed the 2.0.3.0 version from another machine. This caused obvious problems wduring deployment.
After noticing the source of the erro, I went to my original machine and grabbed the DLL and put it on the deployment machine. IT still kept popping out with the same error. Damn, this was funky - so I checked the version of the DLL file. The additional description right below the file in XP showed me 2.0.5050.0 Not knowing any better, I simply changed the number in the web.config. That did not work either. After a couple of hours of frusturation, I ran the dll throught the MS diassembler (ILDASM.exe) That is where it showed me that the version number was actually 2.0.3.0 and not 2.0.5050.0. That was it! I changed the number to 2.0.3.0 and it was golden
So, what's the moral of the story? Iif you run into any version problems pass the dll through the disassembler to learn the true version number :)