There are several ways, depending on how you are working.
When working with Code First + Migrations your database will be created automatically, Migrations generates the scripts and controls the versions of the database.
I believe you are not using the resources mentioned above, but the tip for next projects :)
For your current project, the best way is to generate the scripts and do this creation control manually.
To generate the scripts in SQL Server Management Studio right-click in the database > Tasks > Generate Scripts, select all tables and the location for export.
After that, you place this script in a class of your project and when you start your connection with the bank do a check or an exception treatment to validate if the database does not exist (Each connectionstring model asks for a different approach, if it has the database name in its connectionstring it will have to handle the exception), then if there is no database, it runs the database creation script.
Also create a class with insert scripts to run immediately after database creation.
Do you want to send the bank? Why not send your structures (tables and views) and programming (triggers, functions and procedures)? Or do you want to send data as well? The best of the worlds is you, for this type of distribution and maintenance, have the sql scripts for creating the objects and inserting the data in the project
– Jefferson Quesado
I would like whoever downloads my application just run the solution and ready, at the moment if I run it on another computer it runs but without doing the GET, POST, etc on Sqlserver.
– Felipe Cardozo
And I ended up not answering the question... I would like it to already be a data yes, but it is not something so fundamental. I will give a search on SQL scripts, if you have any documentation I will be grateful.
– Felipe Cardozo