I installed Oracle 11g home edition. I read that to use Oracle data access via .NET, I must install "Oracle ODAC" from http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
The readme text file mentions that "The files of this zip file is NOT to be installed on top of an existing Oracle Universal Installer (OUI) based Oracle Home installation"
I don't understand. How am I supposed to get Oracle.data.access.dll for the existing Oracle install then?
I used setup.exe file to update the database and checked the option to install .net option. It worked then.
Related
I had developed a WPF application, and its backend is a SQL Server CE .SDF file. In setup and deployment project I added .SDF file in it
The issue is: to access and get records from the .SDF file we require an additional software. Please find the below Link
https://www.microsoft.com/en-in/download/details.aspx?id=17876
It has 2 exe files
64 Bit
86/32 Bit
Visual Studio directly installs this software when we install VS
On a client system, I didn't find these files so I am unable to access the .SDF file and get records from it
I need to Copy these files in Application folder and Automatically Install it if the above software is not Present in the PC
Now I am Manually Installing these software(exe ) in Each PC
You're mistaken - to deploy a SQL Server CE 4.0 based application, you do NOT need to deploy and/or install any additional software to your client system - it suffices to include the necessary, relevant SQL Server CE 4.0 DLL's into your application (into the bin or lib folder or something), and just ship those files with your application. That's all you need - no server-side or client-side install needed ! (That's the WHOLE POINT of using SQL Server CE, after all!)
See these links for in-depth descriptions of how to do it:
Right here on Stackoverflow:
How to deploy SQL Server Compact 4.0
Another way to do it:
How to deploy the SQL Server Compact Edition software locally
Official MSDN documentation:
How to deploy a SQL Server Compact 4.0 database with an application
How can I publish a C# project with a .mdf database? I would like that it can be setup easily and need not install a sqlserver. Do I need to change to .sdf?
The Project only uses it in local.
.MDF files are SqlServer main data files, i doubt you can use them without SqlServer installed, as for SqlServer Compact Databases (.sdf) they can be used like you want but converting from one to another isnt just a matter of changing the extension, they are db with different formats.
You would need to create a new .sdf and replicate the schema you have in your .mdf and then copy your data somehow, also you would need to adapt your project since access to data on an .sdf is different than an .mdf not to mention .sdf doesn't support all the things that .mdf does
Why don't you simply deploy your application with .mdf file along with a SQL Local DB installation on user machine who doesn't havd Visual Studio installed?
Make sure you install proper LocalDB. i.e. x86 version of installer on 32 bit and x64 installer for 64 bit machine. There is two different installer for both achitechture.
Sql Server is not installed as part of Windows installation, so you cannot use an *.mdf file in your app unless Sql Server has been installed and you have appropriate permissions for it.
It is possible to distribute either Sql Server Express Edition or Sql Server Compact Edition (recommended) with your app.
MDF files are part of SQL server databases. Without SQL Server (or Express), you can't use them.
If you need an embedable database, SQLite is a good option. Firefox also ships with an embedded SQLite instance, so it's a good/proven option. SQLite also integrates well with ADO.NET; I wrote an article on that here.
I have developed a Windows-based project using C# and MySQL. Now I want to deploy this project to my client.
How to create an Installer (package)?
How to dump the database into the client's system?
Note:
Applications will be installed across multiple systems -- each system has their own database
System doesn't have MySQL installed (installation is not preferred).
This is a completely standalone application, not related to any servers.
Problem: I cannot ask the end user to install MySQL in their system to be able to export, dump, and import in every system.
Required: A package installer which installs my project along with MySQL patches and required data in database.
You can create an installation package using install shield
Other alternatives
http://karcollection.blogspot.in/2012/05/mysql-silent-installation-in-windows.html
http://karcollection.blogspot.in/2012/05/mysql-silent-installation-in-windows.html
Hi have you used MySQL just because its a freely available database product?
by the sound of what your asking would SQL CE not be a better database option?
http://en.wikipedia.org/wiki/SQL_Server_Compact
As far as i know with SQL CE you can embed the database into the application and would not need to install a database server on the client computer.
I'm trying to connect to IBM DB2 database with C# application. At first I've installed IBM Data Server Driver Package, which, according to the documentation is for applications using ODBC, CLI, .NET, OLE DB, PHP, Ruby, JDBC, or SQLJ, use IBM Data Server Driver Package. Then I thought I could use IBM.Data.DB2 assembly and happily connect. It didn't work at all, as the app kept crashing while looking for db2app.dll in its current working directory.
Then I installed IBM Data Server Client, which has this dll in "bin" directory, which I added to system path. That didn't help, so I copied it to my app's build directory, and it now works. But I don't think that is correct, as I also had to copy msg\en_US\db2nmp.xml file to my build directory to get exception error texts.
I think it's wrong to copy all these files from DB2 installation, and I should somehow be able to force IBM.Data.DB2 assembly to look for its required files in the system path, not in its working directory. I also think that Data Server Driver Package should be enough, but I wasn't able to do anything with IBM.Data.DB2.dll until I installed the larger Data Server Client.
I assume that the problem is on my end, not with IBM, so I'm doing something obviously or subtly wrong.
My question is: How do I use the smaller IBM Data Server Driver Package with .NET application?
I think you are looking for this information that is available in DB2 manual:
http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/topic/com.ibm.swg.im.dbclient.adonet.doc/doc/c0010960.html
And perhaps this helps also:
http://www.ibm.com/developerworks/wikis/display/DB2/DB2%20and%20.NET%20FAQs#DB2and.NETFAQs-WherecanIfindtheDB2.NETproviderandVSAddins%3F
In general, I think you should've installed IBM Database Add-Ins for Visual Studio from here(Requires IBM Registration):
https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=swg-daivs
I am using System.data.odbc with "Driver={MySQL ODBC 5.1 Driver}" in the connection string. However, I have not realised there is MySQL connector installed on my PC so however I have not referenced it, it doesn work without it.
Now I need to distribute it embed in the app. I have downloaded MySQL Connector/ODBC 5.1 files, but with Add reference it says "The file is not accessible...make sure its valid COM.." etc.
Thank you
MySQL Connector/ODBC is, as the name suggests, just an ODBC driver for connecting to MySQL. It's not specifically designed for .NET and you can't embed it in your .NET applications in any way. It will need separate installation on any machine where you need to use it.
MySQL Connector/Net is a fully managed ADO.NET provider for MySQL. It's tailor-made for .NET and doesn't require the installation of any other software. It's easy to reference and distribute in your .NET applications, you'll just need to use the System.Data.MySqlClient namespace and objects rather than System.Data.Odbc.
You can embed the .NET DLL, but not the driver itself. You'll need to install MySQL Connector on every computer that runs your application.
The only thing u need is Mysql.Data.Dll
You don't need to install the complete connector, everything u need is in there.
That also counts for the end user, they also only need the dll