View Ticket
Not logged in
Ticket UUID: a67f5a16495d5274973059b93367d8b20affaefd
Title: Runtime library dependencies for Framework 4
Status: Closed Type: Build_Problem
Severity: Important Priority: Immediate
Subsystem: None Resolution: Fixed
Last Modified: 2011-09-27 22:50:45
Version Found In:
Like others, I have found upon deployment of my project that some users are getting errors related to SQLite.Interop.dll not being found, which apparently is ultimately due to the fact that the msvcrt libraries are not correct; this is occurring on new Windows 7 64-bit computers; my application is compiled for the x86 target, and of course I'm using those libraries. (Reference

Previously I just did an XCopy deployment of my software, but unless I misunderstand the prior discussion, must now have my users run the installer so they get the correct version of the C runtime libraries? If there is a way to get back to the prior method that allows XCopy deployment (perhaps via "static linking"), that would be much preferred. I understand the arguments about wanting to keep the link dynamic, the the point is that my users have been getting some hard to diagnose errors and the entire objective of development is to NOT have external dependencies (except the Framework, of course) or require the use of the GAC (which is just like OCX dependencies to me).

I'd include the entire mscvr*.dll library if that would fix it. I'll try the suggestion of renaming the _clr0400.dll, but it is difficult to test, because my development machines by definition have the required runtime libraries, but apparently my client's brand new Win7 machines don't always. I don't have the option of going back to because I need Framework 4 support.

Thanks for all your efforts,

Chris Wilson

anonymous added on 2011-09-26 23:00:13 UTC:
Sorry for repeat posts.

One other thing, my clients cannot run the SQLite installer because it requires Admin rights.



mistachkin added on 2011-09-27 22:50:45 UTC:
1) The next release will have include binary packages statically linked to the MSVC runtime library.

2) Installers typically do require administrator access to the machine.