C# Winform Application With MySql as Database Deployement
-
There should be some tutorials out there explaining how to create a .Net deployment (including sub-installs...). This requires some fiddling around though, but it can certainly be done. A second option is to write an install script yourself. This is probably the easiest way. You create a zip folder the people can download with an install.xxx or setup.xxx script that executes the correct install programs included in the zip file. Third option is as you say. It is less user friendly so you're required to write a good reference about how they should install it, complete with troubleshooting guide. Hope this helps.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
-
V. Thanks for your reply, I guess 2nd option will be more feasible for me. Can u guide me to some good tutorials/samples related with my issue? Like MySql and C# winform application. Regards Ahmed
if you're deploying on windows machines any batch or WMI script will certainly do the trick as they run natively. (eg perl or python need the libraries installed) For Unix systems you'll need another script. There are plenty tutorials out there so I advice to choose one and go through it. When you get the hang of it you need to check how to install MySql and .Net assmblies through command lines. Google will present more information then I can. There is no quick solution I can give you as this custom for your situation. Google is your friend. In this case, there is no shortcut or quickfix, this will have to go via the hard way...
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
-
if you're deploying on windows machines any batch or WMI script will certainly do the trick as they run natively. (eg perl or python need the libraries installed) For Unix systems you'll need another script. There are plenty tutorials out there so I advice to choose one and go through it. When you get the hang of it you need to check how to install MySql and .Net assmblies through command lines. Google will present more information then I can. There is no quick solution I can give you as this custom for your situation. Google is your friend. In this case, there is no shortcut or quickfix, this will have to go via the hard way...
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
V. Thanks for your reply again, despite of fact that there are no quickfix or shortcut, and if choose between WMI Scripts or batch, end-use still have to download the complete bundle alongwith MySql server, if the server installation is required. Only then will batch or script will work.
-
V. Thanks for your reply again, despite of fact that there are no quickfix or shortcut, and if choose between WMI Scripts or batch, end-use still have to download the complete bundle alongwith MySql server, if the server installation is required. Only then will batch or script will work.
-
No, you install the server. The end user just needs to install the client. Perhaps only some dll's are necessary, perhaps it's worth while to look that up.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
Ahh...I think I've not make myself clear regarding my issue. This application is not for my organization, it is commercial software, general purpose accounting application. So any organization that needs it will download from website and do the install (server or client). I need to provide them some quick and easy way to do both installations as an when required. For server PC, the installation will be Application + MySql Server and for client PC only Application required.
-
Ahh...I think I've not make myself clear regarding my issue. This application is not for my organization, it is commercial software, general purpose accounting application. So any organization that needs it will download from website and do the install (server or client). I need to provide them some quick and easy way to do both installations as an when required. For server PC, the installation will be Application + MySql Server and for client PC only Application required.
In that case I would just write a disclaimer stating MySQL server is required for this application to run, with a link where you can get it. In principle it is not a part of the application and it's best to avoid "responsibility" for something you don't own.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
-
In that case I would just write a disclaimer stating MySQL server is required for this application to run, with a link where you can get it. In principle it is not a part of the application and it's best to avoid "responsibility" for something you don't own.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
-
But I thought MySql is free or opensource? doesn't that make it freely distributable? Secondly, how about I distribute XAMPP with my application? As it is lot easier to use then to configure/install actual MySql server?
ahmed_one wrote:
But I thought MySql is free or opensource?
It is free, but you don't "own" it? I'm not sure what your problem is here :confused:. MySQL is a fully supported system with documentation, tuning packages, blogs, forums and what not. And yes you "can" distribute it, but if you do, you're basically stating that you will provide support when it doesn't work. IOW if I would use your product and I install the server and it does not work, I will call you. If you tell the user MySQL is a requirement for your application to run, the client needs to install and configure MySQL himself. The first person to call in case of problems are the MySQL people. Also make sure that your installation creates the database ;) I have no experience with XAMPP so I can't say anything about that.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
-
ahmed_one wrote:
But I thought MySql is free or opensource?
It is free, but you don't "own" it? I'm not sure what your problem is here :confused:. MySQL is a fully supported system with documentation, tuning packages, blogs, forums and what not. And yes you "can" distribute it, but if you do, you're basically stating that you will provide support when it doesn't work. IOW if I would use your product and I install the server and it does not work, I will call you. If you tell the user MySQL is a requirement for your application to run, the client needs to install and configure MySQL himself. The first person to call in case of problems are the MySQL people. Also make sure that your installation creates the database ;) I have no experience with XAMPP so I can't say anything about that.
V.
(MQOTD rules and previous solutions)OriginalGriff wrote:
V is absolutely right
Yes that was confusing till now...Thank you... So then I will let the user know that MySql is must for using the application. Or point them to XAMPP so that they only need to download the package without having the trouble of configuring it, it's just download and run, so it will be much less hassle for them. Thanks a lot for your guidance. Regards Ahmed
-
Yes that was confusing till now...Thank you... So then I will let the user know that MySql is must for using the application. Or point them to XAMPP so that they only need to download the package without having the trouble of configuring it, it's just download and run, so it will be much less hassle for them. Thanks a lot for your guidance. Regards Ahmed