View Ticket
Not logged in
Ticket UUID: 07ab75483c5f05e4b9d3291f5aadf8f72c1f4a1f
Title: Cannot install VS 2008/2010 design-time components side-by-side
Status: Open Type: Feature_Request
Severity: Important Priority: Low
Subsystem: VsDesignerInstaller Resolution: External_Bug
Last Modified: 2012-12-24 00:16:13
Version Found In:
User Comments:
anonymous added on 2012-12-18 16:54:46:
I installed the package sqlite-netFx40-setup-bundle-x86-2010- and checked the options to integrate with VS2010. However, the installer did not add the necessary provider, despite me ensuring that the required options were checked.

mistachkin added on 2012-12-19 01:02:52:
I just tested this installer myself using Visual Studio 2010 on Windows XP.
Could you provide more details about the target system and the log files from
the installation, etc?

The log files should be located in the %TEMP% directory on the target machine.
They will have names similar to "Setup Log 2012-12-18 #001.txt" and

Also, the "Installer.exe.trace.tmp*.log" log file should end with entries
similar to:

Installer.exe: #105 @ 2012.12.19T00:56:37.1083328: Installer.Main: subKeysCreated = 12, subKeysDeleted = 1, keyValuesSet = 20, keyValuesDeleted = 0
Installer.exe: #106 @ 2012.12.19T00:56:37.1083328: Installer.Main: Success.

anonymous added on 2012-12-19 13:26:39:
Found the issue - it seems the .NET 4.0 package doesn't work properly when installed after the .NET 3.5 package. I had to remove all versions of System.Data.SQLite, then install *only* sqlite-netFx40-setup-bundle-x86-2010- That got everything working properly.

Either this needs to be documented on the downloads page, or the installers need fixing to allow side-by-side installs. MS does it with the entire .NET Framework, so surely it can be done for a single assembly.

mistachkin added on 2012-12-20 01:24:45:
I think the root of the problem is the requirement to place the System.Data.SQLite
assemblies into the GAC (which is only side-by-side if the assembly versions
differ).  In this case, the assembly versions are all "", by design.

I'm not sure that I see a clean way around this.  Therefore, I'm changing this
ticket into a feature request to prevent it from blocking the release.