Transfering VB.NET program to another PC

Question

0.00/5 (No votes)

See more:

SQL-Server-2014

I created an app in Visual Studio 2019 using VB.NET and I have a .dbo database on SQL Server 2014 Management Studio on my PC its working fine. The problem here is I want to send this app to a customer to import the database and run the program. Do I have to change the connection string on his computer or something else to run the program perfectly? Or the best way to avoid this is making the app .exe and send it to him

What I have tried:

i have tried to make it in .exe form but the error was that the database can not be found anywhere

Posted 22-Apr-20 6:52am

Member 14810219

Updated 22-Apr-20 7:02am

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

RickZeeland · Answer 1 · 2020-04-22T07:03:00

Your customer needs to install SQL Server 2014 if you did not distribute it with your application.
SQL Server is notoriously hard to package and distribute with your application, if your needs are simple you could use LiteDB which is just a single .dll file, see:
best-databases-for-a-small-net-application~litedb[^]

Another problem with SQL Server is that there are many versions and different ways to connect, which leads to a lot of confusion.
So discussing all this here is not a good idea, it would be better to read a book or maybe start here: how-to-open-a-sql-server-database-by-using-the-sql-server-net-data-pro[^]
how-to-create-a-sql-server-database-programmatically-by-using-ado-net[^]

Using an .mdf file is not a good idea, it is better to create an SQL script (e.g. from Sql Server Management Studio) and create the database from your application.
See: Execute CREATE TABLE from SQL script File in VB.net[^]

If you are using LocalDb this needs to be installed too, see: sql server - LocalDB deployment on client PC - Stack Overflow[^]

Also see: DBO or MDF whats the diffrence? | The ASP.NET Forums[^]