Sql server compact 3.5 sp2 failed to install
- Sql server compact 3.5 sp2 failed to install full#
- Sql server compact 3.5 sp2 failed to install windows#
Sql server compact 3.5 sp2 failed to install windows#
A number of developers are still, in 2017, developing new solutions for Windows CE / Windows Mobile using Visual Studio 2008 and SQL Server Compact 3.5 SP2. Honestly, a bit embarrassing and a pretty amateur move where some vigilance could have saved me quite a bit of aggrivation.ĮNSURE YOU’RE DEPLOYING ALL THE SAME PACKAGES ON ALL DEVELOPMENT MACHINES! JUST BECAUSE SOMETHING ALREADY EXISTS ON ONE MACHINE, DON’T ASSUME IT’S THE SAME VERSION! Author Ryan McCauley Posted on FebruApCategories.
Sql server compact 3.5 sp2 failed to install full#
I confirmed this by running the SP2 for Windows Mobile installer, and it patched my DLL right up to the full SP2 version – problem resolved, and the project now opens up on both workstations with no need for any DLL reference swapping. While I’d installed VS 2008 SP1 on both machines, I’d installed the actual SQL Compact 3.5 SP2 for Windows Mobile (EDIT : This link has been updated to the current location for this download) package on only one machine and not the other – this left the DLL on one machine patched to SP1 (courtesy of Visual Studio) and the other machine with a fully-patched SP2 DLL (courtesy of the actual SP2 Windows Mobile installer). As it turns out, Visual Studio 2008 RTM deploys SQL Compact 3.5 RTM (.0), and applying Visual Studio 2008 SP1 patches that to the SP1 version (.0) – notice the VSToolsVersion/ VSToolsServicePackLevel values in the registry location above, which reflect your current service pack level of Visual Studio 2008. So how did I end up with the SP1 version installed on one machine, but not on the other? Since I’d installed SQL Compact SP2 on both machines, I was baffled. Here are the version numbers I found (for the various components): There, you’ll find a combination of “Version” and “ServicePackLevel” entries for every SQL CE component you have installed, and it will shed some light. HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server Compact Edition\v3.5\ENU Or if you want to see x86 components installed on your 圆4 machine: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server Compact Edition\v3.5\ENU To find out why, I had to dig into the registry, where I found all kinds of version information about the SQL Server Compact Edition components I’d installed, the DLL version, and the service pack levels: There, I found my issue – that file version was a different version on each machine (.0 on one and. X64: C:\Program Files (x86)\Microsoft SQL Server Compact Edition\v3.5\Devices\ X86: C:\Program Files\Microsoft SQL Server Compact Edition\v3.5\Devices\ It turns out that when you add a reference to this DLL in a Compact Framework project, Visual Studio is using the following version (depending on whether you’re on an x86 or 圆4 machine): However, searching for details on the different versions of this DLL in the wild wasn’t fruitful – did I have SQL Compact 3.5 RTM installed (3.5.0.0)? If I’d installed v3.5 SP2, why was it shown as 3.5.1.0 (shouldn’t it be 3.5.2.0?) on one machine, but as 3.5.0.0 the other? To top that off, both versions (v3.5.0.0 and v3.5.1.0) were in my GAC as MSIL – what? 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.