I am deploying a VB.net 2010 winforms application, and when I install it on the client's machine, the install process also installs an instance of SQL Server 2005 Express. The application connects to a central SQL database on the server. To install, I am using the "Publish" option in VS 2010
Why does it do that? There should be no need for a local instance of SQL Express. Is there a way to avoid installing SQL 2005 Express (I know it is free, but I would rather not have it installed if possible)
It's likely that whatever technology you're using for packaging/deployment is including the installer for SQL. For the default setup project, I believe it is a checkbox for a pre-requisite.
Related
I have a client application that will be deployed using ClickOnce. The client application will connect to a local sql database on their machine. They will need sql server 2008 express installed upon installed and the .mdf file attached.
I set Prerequisites to include sql server 2012 express.
So I would like the application when installing to check if sql server already installed with the database. If not then install and attach database. How can i achieve this properly using click once. I have a vb.net project using visual studio 2013. any references would help thanks.
You just have to change your connection string
to somthing like this
Server=.\SQLExpress;AttachDbFilename=C:\MyFolder\MyDataFile.mdf;Database=dbname;
Trusted_Connection=Yes
now your sql is linked to a specific database file
check this link https://www.connectionstrings.com/sqlconnection/attach-a-database-file-on-connect-to-a-local-sql-server-express-instance/
I have developed a VB.NET application with SQL database, now i want to package it with the database and deploy it on some other machine which does not have SQL installed.
You could use InstallShield - that will allow you to create an installer which includes your program and allows you to install your SQL Server 2008 instance.
I'm actually done doing the small-scale application for our office, however, I really don't have any idea how to deploy this one. Can someone provide me any links on how to do this? This project will be deployed in one pc.
If its a Windows application you need to create a setup project.
If its a web based application, install your application on your web server and provide clients with the appropriate link.
I have developed a application in c# which is windows based application. It stores data into database sql server. I want to know, when I create setup in VS and install it in a client computer should I install sql server software also or Is there any way without installing SQL Server in client's PC My application can function correctly.
sIf you use a filebased implementaion of SQL (localDB) you should be able to get away with a "setup" installing the neccecary dependencies to bootstrap the DB. (Someone correct me?)
If you use the DB in a hosted SQL environment (SQL Server running as a service), you will need to install SQL server on the deployed pc, and get the database up.
I am no sure if you can "automate" installing SQL server and getting the DB up from a setup app.
You have two deployment options for applications that contain SQL Server Compact 3.5 databases. The method of deployment you choose depends on the servicing requirements of your application and whether your users will need administrative credentials on the computer on which the application will be installed.
Following are the deployment options for SQL Server Compact 3.5 databases:
1. Traditional Microsoft Windows Installer (Microsoft setup technology)
a. Users need administrative credentials to install the application.
b. SQL Server Compact 3.5 will be serviced by Microsoft Update.
c. Can use ClickOnce deployment.
-or-
Private file–based deployment (deploying the SQL Server Compact 3.5 DLLs as part of the project)
1. Users do not need administrative credentials to install the application.
2. SQL Server Compact 3.5 will not be serviced by Microsoft Update.
3. Can also use ClickOnce deployment.
Is it possible that can I use Sharepoint server as development machine also. My mananger has asked me to use one of the newly purchased server for Sharepoint server as well as sharepoint development.
In future we will do some small development so what type of installation do I need?
Please guide me for the following which one I should install or which one is not required.
Standalone or Farms
VM
SQL Server 2008
VS 2010
SharePoint 2010 can run on a 64-Bit Windows 7, as per instructions from Microsoft.
It does not work on 32 Bit Windows as SharePoint 2010 is 64-Bit only, and it does not work on Vista.
Yes, it is possible to use your SharePoint server as a development machine. I'd suggest using a VM as it allows you to quickly and easily switch between, revert and deploy setups should something go wrong (and things WILL go wrong with SharePoint).
At work, my machine runs Win Server 2008 and I remote into a Hyper-V hosted VM which itself runs Server 2008 - I develop and run SP on that VM. Since I have SP, SQL Server and VS2010 all running on it at the same time, I allocate the VM at least 5.5 GB of memory (and it's still hungry for more).
You can develop for SharePoint 2010 on a Windows 2008 Server x64 or on a Windows 7 64bit. A Windows 7 is of course only recommended for development.
Most developers use a standalone machine for their SharePoint 2010 development. Creating a farm is complex and $$.
Personally I develop in virtual machines. I have on clean vm image that I copy for every new project (client). You need a powerful computer to run these virtual machines. At least 4GB memory and a recent multicore cpu.
You will need Visual Studio 2010, SQL server and ofcourse SharePoint. Office can also be handy but is not needed. SQl server express is included in Visual Studio and the SharePoint install also installs SQl server if needed. Certain Visual Studio versions include an "SQL server developer" license.