We currently have a XAP file which contains Foo.dll, and another XAP file (with a completely different name) which contains an updated version Foo.dll (but the same version number).
When we run the second XAP file, it looks as though the Silverlight runtime on the client, is picking up the old version of Foo.dll from the first XAP file.
Anyone know where the Silverlight runtime unzips the xap file before running its content? Or if the runtime executes on a single app domain which could explain these errors?
It is always single app domain till your create a new one.
Specify Version number in AssemblyInfo.cs, then use Reflection to get it from your SLV application.