LINQ-to-MySQL with DbLinq in C# - Final Thoughts
(Page 4 of 4 )
As you can see, we have arrived at the end of this article. By now you should have completed your first .NET application in C# based on the DbLinq provider. Keep in mind that the example presented in this article heavily depends on the tables contained within the database (their fields, types, etc.).
This means that you should pay extra attention when implementing everything in correlation with your database and your specific needs. This is possible only if you understand the basic concepts of LINQ, have the necessary experience with RDBMS, and, of course, are familiar with working with Visual C#. You can always refer back to the official Microsoft LINQ documentation should the need arise.
Moving on, here's one final screen shot of the application up and running after the "List Clients" queries has been executed. In a nutshell, the entire process isn't a black art. The DbLinq provider does a really good job as long as the queries remain simple, as they did in this article. Once they become complex and have sub-queries, things change...
Another thing worth mentioning is that at the time of writing, DbLinq has a huge limitation, and that's not being able to handle more than one foreign key. Surely, foreign keys aren't necessary theoretically-you can read about this here, here, and here-but that's an ugly workaround with which we don't really like to deal. The project requires further development, and this will fortunately change in the near future.
Meanwhile, you are free to explore other LINQ-to-other database providers. Every so often check the status of currently available providers and hope for the best. You should also refer back to the previous article in this series-the one that covered other providers along with DbLinq such as the LightSpeed(by Mindscape) and NHibernate.
And finally, we can't really finish without inviting you to join our helpful forums at DevHardware Forums. We've a strong base of resident professionals, enthusiasts, and tech experts. If you want to hear opinions on some service or ask for some clarification regarding some details, just shoot us your questions. We'll do our best to help. And you may also want to pay a visit to the forums of our sister-site: DevShed Forums.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
/ 10 
