[dba-VB] VB.Net - using an outside DLL

Yes it doesn't matter where you place  ICSharpCode.Sharplib.DLL because when
you create a reference for this DLL in your project you will be asked for
its location. After you point VS.NET to the correct location it will place a
copy of that DLL in the same BIN folder where VS.NET will place your
application DLL or EXE after it compiles and links it.


-----Original Message-----
From: JWColby [mailto:jwcolby at colbyconsulting.com] 
Sent: Wednesday, May 02, 2007 8:55 AM
To: ebarro at verizon.net; dba-vb at databaseadvisors.com
Subject: RE: [dba-VB] VB.Net - using an outside DLL

SO IOW it doesn't matter where I place the DLL.  And yea, it probably was
mentioned in a previous email.  I am starting to understand enough to
comprehend the previous emails.

John W. Colby
Colby Consulting
www.ColbyConsulting.com

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of Eric Barro
Sent: Wednesday, May 02, 2007 11:30 AM
To: dba-vb at databaseadvisors.com; 'Access Developers discussion and problem
solving'
Subject: Re: [dba-VB] VB.Net - using an outside DLL

In VS.NET you create a reference to the DLL and when you compile your
project it puts it in the BIN folder. When you create a setup you specify
all the files it needs and the setup program knows where to copy it on the
target machine. 

I believe I've covered this in a previous email about where .NET stored the
binaries.

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of JWColby
Sent: Wednesday, May 02, 2007 8:21 AM
To: 'Access Developers discussion and problem solving';
dba-vb at databaseadvisors.com
Subject: [dba-VB] VB.Net - using an outside DLL

I am looking at using the ICSharpCode.Sharplib.DLL for its unzip stuff.
This is actually something that is going to go on the server I am building
the project on but might also go on another machine.  My question in general
is where do you place a component like this in the .Net universe?  Do you
place it in Windows\System32 like you would all other DLLs?  Do you place it
in the framework directory?  Do you place it in the project specifically
using it?  
 
Regardless of where you place it, how is it "gathered up, and then
reinstalled" on another machine as a project is migrated to another machine?
 
John W. Colby
Colby Consulting
www.ColbyConsulting.com