Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I'm having trouble setting up Visual Studio and my Web Service hosted on the Azure platform. My webservice needs to connect to an AzureDB.
The troubles begin when i try to Code first migrate my data models into my Azure database. I'm not sure how this is done, because when i try to do it in the Package Manager, it keeps doing it on the local database, and not on the Azure database. The guides i've found seems to be outdated, or not working with VS2019 somehow.
The update-package command picks up the connection string from your "startup" project in your solution, which is likely to be your website.
So you could update the connection string in there, and if your permissions are correct, you'll be able to deploy to the remote database.
What I would suggest is look into to doing a proper pipelined solution, where the migration runs as part of a deployment to an environment.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I'm currently creating a Web Service to call on my ASP/C# application, which has a basic SQL SELECT query from an Oracle Database.
The problem is that the Web Service file itself doesn't recognize the Oracle libraries, so I can't use any commands like OracleConnection and such, as they asked me to do so for work.
The commands itself work perfectly on C# pages, and have no issue at all. The Web Service can read SQL Commands like SqlConnect, but not OracleConnect.
Any way to fix it? Thanks.
I was also facing all same issue
so i upload the all assemble to server it resolve my problem also please check the all the references
then clean the solution and rebuild solution.
Please check the oracle version and reference dll version
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I am new at programming and I want to make an app which uses a SQL Server database. Most important feature of this database must be usable for every computer which has the app installed.
I mean, when I give this app's setup file to another person, this person should be install my app without installing SQL Server program, extra things etc. I don't know it is possible.
I created a database with "SQL Server Object Explorer" inside of "(localdb)\MSSQLLocalDB" but when I tried to add new connection, server name was empty. So I didn't import a database to my project.
So how/where can I create and import a database ?
If you want a local SQL database with your application, that is: data is not shared between devices or users, you'll want something like SQLite which is designed for embedding in distributed applications.
To use it you need to link against the binary and include the binary in your application package. Or, you can use the SQLite team's native C# SQLite library. See here: https://system.data.sqlite.org/index.html/doc/trunk/www/index.wiki
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I create an application using C# and SQL Server database, when I try to create the setup I realized that I need to install SQL Server and create the database in every computer that I install my app on.
Is there any way or software can create the setup with the database without install the SQL server in other computers?
If your storing data locally you are better off to use SQLite (as Flat Eric mentioned, it needs no installation and it efficient on small DB's) then you can just copy the .mdf files instead of having to install the entire SQL server on every machine. Visual Studio provides great functionality to help you set up a LocalDB.
Here are two useful links, They really helped me in these situations:
Upgrade to LocalDB
Creating a Local Database File in Visual Studio
Connecting to Data in a Local Database File (Windows Forms)
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I'm having trouble creating an installation program for my Winforms application. I am using the Windows Installer and the publish function. It creates a nice setup program. After I run the setup on a client machine, I want to update the App.config file to point to a different database than was used for the setup. I have this setting in the app.config file. However, I am not able to update the app.config file on the client's machine. Temporarily, I am creating a new build when I want to change the database that the application points to.
Duplicate of...
Setup App.Config As Custom Action in Setup Project
?
The answer looks good...
http://raquila.com/software/configure-app-config-application-settings-during-msi-install/
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I am currently writing a program in C# that will connect to a database for various user data. The query I have at the moment is what would be the best practice to be able to connect to various databases from the program at runtime?
To clarify:
I may want to connect to Oracle R12, or MS SQL Server or maybe even a dumb old access database. I am fine with putting the connection methods into their respective classes, but what I really want is a config file to be packaged with the application which dictates the type of server used for each installation, the field naming convention, etc.
So should this connection file be a .dll? an encrypted text file? or something else?
Obviously I dont want the end user ready access to the connection details in case they try and do their own digging in the database outside of my application.
I would go with encrypted configuration section, it's pretty standard and there are many examples, here is MS documentation:
http://msdn.microsoft.com/en-us/library/89211k9b%28v=vs.80%29.aspx