Eric Barro
ebarro at verizon.net
Wed May 2 10:29:43 CDT 2007
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 _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com