MySql.Data.dll no longer copied locally?
Posted by: David
Date: December 14, 2004 09:49AM

Hi Reggie,

With 1.0.2, the MySql.Data.dll file was automatically copied to the bin folder(s) of my projects when I referenced it in via Visual Studio. I noticed this morning with 1.0.3 that this is no longer the case. Is that by design?

If you look at the properties of the reference, it points to the location on the hard drive of my dev machine where the .dll is installed, much like the ByteFX driver in the past.

If this is by design, then I can install the driver on our production server, and I no longer need to copy the .dll over to the respective bin folders for each of the projects?

This is not necessarily a bad thing, I would just like to know if this behavior will persist to the final release of the driver so I can coordinate with the staff that manages our production server.



Options: ReplyQuote

Written By
MySql.Data.dll no longer copied locally?
December 14, 2004 09:49AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.