I always deliver mysql.data.dll in the bin folder with all my applications other dll's -
that way your deployed application always uses the correct version. This does (I presume)
rely on the fact that the deployment machine has not had a different .Net Connector dll
installed in the GAC separately. There should be no real reason to install the connector
separately on the deployment machine. Why would your users do this? Are they developers
too?
-----Original Message-----
From: Fahad Khowaja [mailto:fahadkhowaja@stripped]
Sent: 03 October 2006 10:11
To: dotnet@stripped
Subject: How to bundle .net driver with application
Hello everyone!
Im new to this list. I have developed an application in C# which accesses a
MySQL database using the .NET connector. I have two questions:
1) My development machine has the 1.0.4 version of the connector installed
and the application was built against this. A test machine I ran my program
on had the 1.0.7 version of the connector. On this machine, my database
thread wont even start. I downgraded the connector to 1.0.4 and the program
started working fine. Can an application only work with the same version of
the connector it was built against?
2) Some of my users who have to run this program will not have the right
connector version installed. Is there a way to package the connector along
with the application so that when the user installs the application it gets
installed automatically and the user doesnt have to worry about getting the
right connector version?
Thanks,
Fahad.
--
MySQL on .NET Mailing List
For list archives: http://lists.mysql.com/dotnet
To unsubscribe: http://lists.mysql.com/dotnet?unsub=1
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.407 / Virus Database: 268.12.11/460 - Release Date: 01/10/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.407 / Virus Database: 268.12.11/460 - Release Date: 01/10/2006
