How to make Setup Project
-
Greetings I'm using InstallShield for deploying projects and I'm new in using it I need to know how to include some applications and executable files to be installed while installing my application what I mean is that I need to include for example the .NET framework 4.0 so if it does not exist at the client it is installed during the installion of my application as well as the SQL Server Express edition. Finally as the big picture of what I want to do is like making a setup project that is when installed it installs with it other applications needed by my application like .NET Framework and SQL Server for the database as well as attaching the database to the SQL Server instance. So when the client starts to setup my application when finished it uses the application without the need to setup other application or attaching the database to the SQL Server
-
Greetings I'm using InstallShield for deploying projects and I'm new in using it I need to know how to include some applications and executable files to be installed while installing my application what I mean is that I need to include for example the .NET framework 4.0 so if it does not exist at the client it is installed during the installion of my application as well as the SQL Server Express edition. Finally as the big picture of what I want to do is like making a setup project that is when installed it installs with it other applications needed by my application like .NET Framework and SQL Server for the database as well as attaching the database to the SQL Server instance. So when the client starts to setup my application when finished it uses the application without the need to setup other application or attaching the database to the SQL Server
You should not include SQL Server in your installation. There are a couple of reasons: 0) You can only distribute SQL Server Express for copyright reasons - not SQL Server full version. 1) They may already have SQL Server installed on the network. If so, then they will presumably want to use that version. 2) If they do have SQL server installed and you start proliferating SQL server Express instances, you are going to annoy the heck out of the database administrator... 3) A single site installation of SQl Server is a lot more likely to be backed up than a number of scattered version under user control. 4) Sql server is quite complex for a "normal" user to install and administer - it is not a good idea! 5) It will destroy the primary advantage of using Sql Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
You should not include SQL Server in your installation. There are a couple of reasons: 0) You can only distribute SQL Server Express for copyright reasons - not SQL Server full version. 1) They may already have SQL Server installed on the network. If so, then they will presumably want to use that version. 2) If they do have SQL server installed and you start proliferating SQL server Express instances, you are going to annoy the heck out of the database administrator... 3) A single site installation of SQl Server is a lot more likely to be backed up than a number of scattered version under user control. 4) Sql server is quite complex for a "normal" user to install and administer - it is not a good idea! 5) It will destroy the primary advantage of using Sql Server over SqlCE or SQLite - multiuser access. If everyone installs their own copy of SQL server, then you will have multiple copies of your database, each used by a single person. This will cause some confusion, and (depending on how you wrote the original database) may take some considerable effort to combine into a single instance when the problem is realized.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
What is the client does not have a SQL Server on his machine and the application require the database so he will have to install a SQL Server on his machine then he will have to attach the database himself. I need to make a single setup file as the software you buy e.g Microsoft Dynamics you do not have to install a separate SQL Server and to attach the database yourself. However, you give me a hint to query if there is an instance of SQL Server on the client machine if there is no instance I need only to setup the express edition to make the program running
-
What is the client does not have a SQL Server on his machine and the application require the database so he will have to install a SQL Server on his machine then he will have to attach the database himself. I need to make a single setup file as the software you buy e.g Microsoft Dynamics you do not have to install a separate SQL Server and to attach the database yourself. However, you give me a hint to query if there is an instance of SQL Server on the client machine if there is no instance I need only to setup the express edition to make the program running
SQL Server is a complicated beastie, and it really isn't that simple to install and administer: it's very easy to get it wrong and cock the whole thing up. And most users aren't aware of it's existence in their LAN environment. So ask yourself this: "Do I need SQL Server?" Or would you be better off using a single user database which requires no installation, administration or maintenance? Because if you aren't using the multi-user facilities of SQL Server, then you are using a sledgehammer to crack a nut. And if you do, then you need to ensure that someone competent installs and maintains it because otherwise you are going to give your users horrible problems down the line... Seriously: don't install it for them.
Those who fail to learn history are doomed to repeat it. --- George Santayana (December 16, 1863 – September 26, 1952) Those who fail to clear history are doomed to explain it. --- OriginalGriff (February 24, 1959 – ∞)
-
Greetings I'm using InstallShield for deploying projects and I'm new in using it I need to know how to include some applications and executable files to be installed while installing my application what I mean is that I need to include for example the .NET framework 4.0 so if it does not exist at the client it is installed during the installion of my application as well as the SQL Server Express edition. Finally as the big picture of what I want to do is like making a setup project that is when installed it installs with it other applications needed by my application like .NET Framework and SQL Server for the database as well as attaching the database to the SQL Server instance. So when the client starts to setup my application when finished it uses the application without the need to setup other application or attaching the database to the SQL Server
