Using SQL Application in network
-
Hi Developers I decide to develop an application with C# which uses SQL server express edition. My application shall works on the local network and some workstations use the SQL data simultaneously. Beforehand I developed similar application with ODBC technology. I pursue better idea, So I listen your good recommendation.
Best Regards, Reza Shojaee
-
Hi Developers I decide to develop an application with C# which uses SQL server express edition. My application shall works on the local network and some workstations use the SQL data simultaneously. Beforehand I developed similar application with ODBC technology. I pursue better idea, So I listen your good recommendation.
Best Regards, Reza Shojaee
-
how about sqlconnection [^]
You can use sqlconnection for local client and odbcconnection for remote client
Best Regards, Reza Shojaee
-
Hi Developers I decide to develop an application with C# which uses SQL server express edition. My application shall works on the local network and some workstations use the SQL data simultaneously. Beforehand I developed similar application with ODBC technology. I pursue better idea, So I listen your good recommendation.
Best Regards, Reza Shojaee
Depends how big your project is but it is worth Looking up LINQ to Entities and NHibernate. These are both ORM frameworks that allow you have a relational database, whilst living in the object world on the C# side. After this, LINQ to SQL is a possible, lighter weight choice. Finally you could use straight ADO, but in a good implementation this alone can be cumbersome. NHibernate currently has better features, but long-term LINQ Entities might be the pony to back, as the framework is by Microsoft, and comes with .NET 3.5 as standard.
Cpianism: I have a negative number in my Rep so please fix it. Chris Maunder: That isn't a bug.
-
Depends how big your project is but it is worth Looking up LINQ to Entities and NHibernate. These are both ORM frameworks that allow you have a relational database, whilst living in the object world on the C# side. After this, LINQ to SQL is a possible, lighter weight choice. Finally you could use straight ADO, but in a good implementation this alone can be cumbersome. NHibernate currently has better features, but long-term LINQ Entities might be the pony to back, as the framework is by Microsoft, and comes with .NET 3.5 as standard.
Cpianism: I have a negative number in my Rep so please fix it. Chris Maunder: That isn't a bug.
Hi My friend My project isn't very big, But I like new experiences. Beforehand I heard about LINQ but NHibernate is unfamiliar technology for me. My project is a windows application, these technologies only use for web or no? Do you know good example of these technologies ? :)
Best Regards, Reza Shojaee
-
Hi My friend My project isn't very big, But I like new experiences. Beforehand I heard about LINQ but NHibernate is unfamiliar technology for me. My project is a windows application, these technologies only use for web or no? Do you know good example of these technologies ? :)
Best Regards, Reza Shojaee
Reza Shojaee wrote:
My project is a windows application, these technologies only use for web or no
These technologies are intended to allow .net applications (of whatever type) to communicate with the database. As long as you can connect to the database across your network, they should be fine.
Reza Shojaee wrote:
Do you know good example of these technologies
I suggest either doing a search on this site (I'm sure there are some excellent articles around), or googling for them. I started using these a while back, so I haven't looked at introductory articles in a while.
Cpianism: I have a negative number in my Rep so please fix it. Chris Maunder: That isn't a bug.