On Tue, Feb 26, 2013 at 5:37 PM, Gilles Ganault <gilles.gana...@free.fr>wrote:
> On Tue, 26 Feb 2013 13:09:10 -0500, Kevin Benson
> < kevin.m.ben...@gmail.com> wrote:
> > Because there are actually a number of different ways the (CLR)untime
> > locates assemblies, I ~believe~ the FAQ only attempts to offer a general
> > advisement about the "Externals" folder as a *HINT*. The rest is up to
> the
> > programmer.
>
> Thanks for the link to MSDN, but it doesn't mention \Externals, so the
> application won't find the other DLL since it's neither in the
> application directory nor in the PATH.
>
The directory doesn't *HAVE* to be called ...\Externals. You pick the name,
any name, and then tell Visual Studio, that is all ;-)
The FAQ is just illustrating with a "semantic" name example ...that the
folder(s) would represent "where you store" any/all external files
associated with your project/solution. I ~believe~ the histrionics of
Visual Studio C++ discussions reference /Externals, so that example
name likely originates somewhere back in time and actual usage.
--
--
--
--Ô¿Ô--
K e V i N
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
