|
Thank you !
ok , let's forget the first reason.
but what about the second reason , it's possible to connect to another database on another server with app.config file ?
if there's please help me with some information.
Thank you !
|
|
|
|
|
You can put a mostly configured connection string in the app.config. This "template" connection string can have replaceable tags in it to put in a server\instance name and a database name. When you need the connection string, load it (ConfigurationManager class), replace the tags with the appropriate names (it is just a string afterall) and then you can use that in your database code.
|
|
|
|
|
Thank you !
I can do that , but in this case what is the purpose of app.config file , just to keep a string that I read and I change in runtime.It's the same with the case i construct the entire connection string during runtime.
Or is better to change the replaceable tags directly to app.config file and keeping the Dbcontext unchanged without passing the connection string as parameter ? Is possible this ?
Thank you !
|
|
|
|
|
Don't change the tags in the app.config file. Users cannot change anything in Program Files, so your code will not be able to change it either.
Code always runs AS THE USER that launched it.
|
|
|
|
|
Thank you !
But my application folder isn't on Program files.
The folder is c:\MyProgram.
So in this case do you think that I can change the app.config file ?
Thank you !
|
|
|
|
|
System Admins don't like that, so if you're deploying your app in a corporate environment, I'd think twice about that.
|
|
|
|
|
No problem about this .
My question is simple : Is there a problem to change the content on app.config ? If yes this file should be treated as text file during manipulation ?
Thank you !
|
|
|
|
|
No, but it's just an XML file.
But, once you replace the tags in the app.config file, you don't have known tags to look for any more.
|
|
|
|
|
dilkonika wrote: can open it
"Can" and "do" are very different things. If they don't then it's not a problem.
You'll never get very far if all you do is follow instructions.
|
|
|
|
|
Is it possible to create an ODBC Connection for MySql Database using VB .net?
I have searched the net but could not find any information
|
|
|
|
|
can you not use the MySql Connector[^]?
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
Absolutely. I have to use the connector but I am not sure of the code. So in case and link to some sample is available it will be of great help
|
|
|
|
|
It's usually the installer that registers the ODBC connection; has to be done once, not at every start of your app.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Very true. I actually want to put an installer which creates the ODBC Connection. But I am not getting any sample of the code. In case anybody has any link it will be a great help for me
|
|
|
|
|
SPSandy wrote: I am not getting any sample of the code MSDN[^] again, example at the bottom of the page. It's the same pattern as the SqlConnection/SqlCommand examples; create a connection, execute a command with parameters, and read the results.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hello !
I'm using vb.net with sql server. On a foler I have a backup database that is empty (model.bak).How can I do to restore this database with a new name ( DB1) from code in visual basic 2013 ?
Thank you !
|
|
|
|
|
dilkonika wrote: How can I do to restore this database with a new name ( DB1) from code in visual basic 2013 ? One could execute a RESTORE[^]-command with the appropriate parameters. Alternatively, you can use SMO.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hello !
Where can I find some information about doing this process with SMO ?
Because I want to learn both methods.
Thank you !
|
|
|
|
|
dilkonika wrote: Where can I find some information about doing this process with SMO ? There's article's here[^] on CodeProject, and there's examples on TechNet[^].
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
On your opinion , is better to use Transact-SQL or SMO ?
For example :
I'm creating and testing my application on Visual Studio2013 and SQL server 2008R2.
If I need to run my program on SQL server 2005 or SQL server 2012 , will SMO work ?
Thank you !
|
|
|
|
|
dilkonika wrote: On your opinion , is better to use Transact-SQL or SMO ? I tend to prefer scripts; easy to test and update.
SMO would also require a specific version for each version of SQL Server that you want to support. Still, SMO makes it easy to manipulate SQL Server from C#.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Thank you !
I have another question.When I use SMO , I should add to reference some files :
Microsoft.SqlServer.ConnectionInfo.dll
Microsoft.SqlServer.Smo.dll
Microsoft.SqlServer.Management.Sdk.Sfc.dll
Microsoft.SqlServer.SqlEnum.dll
But these files are in folder : C:\Program Files\Microsoft SQL Server\110\SDK\Assemblies\
when I install my application to other computers , can I put these files on application folder or they should be on this folder on destination computer ? But, if I have this application on a client computer that not have sql server installed?
And my last question (Sorry !)
I want to use SMO just for Backup restore operations.I think these are very basic operations.Do you think that one version of SMO (that reference on my application) can support only for these operations even different versions of SQL server (older or newer ?)
Thank you !
|
|
|
|
|
dilkonika wrote: can I put these files on application folder Yes
dilkonika wrote: But, if I have this application on a client computer that not have sql server installed? The SMO-assemblies need to be present, but you don't need Sql Server.
dilkonika wrote: I think these are very basic operations.Do you think that one version of SMO (that reference on my application) can support only for these operations even different versions of SQL server (older or newer ?) You can't use SMO for 2008 on a 2005-server, but the other way around "might" work.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Thank you !
But if I put these files on my application folder , I should change the reference on my application to this directory ?
And if I can do this , let suppose that I run this application on a pc with different version of sql server , is possible only to change these files on my application folder with corresponding files from that version , and may work or I'm wrong ?
|
|
|
|
|
dilkonika wrote: But if I put these files on my application folder , I should change the
reference on my application to this directory ?
No, the reference is not specific to a directory; .NET will look in various locations for an assembly, including your executables working-folder.
dilkonika wrote: let suppose that I run this application on a pc with different version of sql
server , is possible only to change these files on my application folder with
corresponding files from that version , and may work No, that won't work; you write code/compile against the files you referenced. Replace those files and your app stops working.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|