There were some complaints registered previously with windows about this
issue where it looks first in the program root for a DLL and then the
GAC. This is actually unwanted behaviour since if you use a 3rd party
DLL (let's take the library for Google's Chrome browser as an example)
in your pro
I ran this utility and what I discovered is problematic.
On my development machine, it is always looking for this dependency in
the GAC first and loading it from there. as opposed to the start-up
folder where the DLL is located. Why is this looking for the DLL in the
GAC first? This is not no
fuslogvw (
https://msdn.microsoft.com/en-us/library/e74a18c4%28v=vs.110%29.aspx )
might help you understand the DLL binding issue.
On 18 March 2015 at 20:04, Jeff Steinkamp wrote:
> One of my users reported that he was unable to get a piece of software
> that uses this .NET assembly (x86 version
It might also be the runtime; was trying to install a debug version at one
point and msvcr110d.dll was missing... maybe it's just that the required
runtime is missing yet? It also just threw an error 'cannot locate'
On Wed, Mar 18, 2015 at 1:09 PM, Nicholas Smit wrote:
> fuslogvw (
> https://ms
One of my users reported that he was unable to get a piece of software
that uses this .NET assembly (x86 version 1.0.9.6) to run on windows
10. It is throwing an error saying that it is unable to located
system.data.sqlite.dll even though it is included in the same folder as
the program execut
5 matches
Mail list logo