I had a DLL version mismatch – a general problem when you’ve got multiple computers you’re developing something on, since you have to ensure the same versions and packages are installed on each. If this reference is required by your code, you may get compilation errors. Check to make sure the assembly exists on disk.
Could not locate the assembly “, Version=3.5.0.0, Culture=neutral, PublicKeyToken=3be235df1c8d2ad3, processorArchitecture=MSIL”. NET reference list on both machines) and checked it back in, then I’d get the same situation on my first computer with the following error message:Ĭould not resolve this reference. If I dropped the reference, re-added it on my second computer (BTW – only one version was listed in my. Could not locate the assembly “, Version=3.5.1.0, Culture=neutral, PublicKeyToken=3be235df1c8d2ad3, processorArchitecture=MSIL”.
The Problem:Īfter checking the project into source control on one computer and fetching it on the other, I’d see a broken reference to : Missing reference to Īnd I received the following message (and about 100 errors – one for every reference to the namespace in my code) when I attempted to compile:Ĭould not resolve this reference. In researching it, I couldn’t find good information about the different versions of the DLL, so thought some future developers might enjoy what I found out, all in one place. While developing a Windows Mobile device application on two different computers, I thought I’d installed SQL Server Compact Edition 3.5 SP2 on both of them, but ran into some version difference issues.
0 kommentar(er)
