The very first time that I was interested by LinQ, there in 2007, apart from the great admiration for the product and the whole range of possibilities that it was before me, there was something that I really missed something that, for a SQL developer with a "wide" range of acknowledge, was difficult to understand about the new philosophy for queries over objects. It was nothing more than the absence of many of the SQL joins advanced sentences within the LinQ basis class extensive methods.
At the beginning I assumed that the problem was a matter of time for the Microsoft Developer team and that it will be fixed in the next versions. But, the more deep I analysed the product the more I realized that maybe it was not the better way to work for an object oriented developer and that it was needed to leave apart the solutions given for a database proffesional worker since they may be useful for them but not so valid for us. This was remarked even more at the time I knew about Entity Framework browsing properties.
To this day, I learnt that anything is black or white but the main point is to be useful, that some solutions do not fit 100% with the pureness of the development premises but they are very handy and save time and money, which is essential in the daily work for a great developer. We can find some examples of it within the Framework (Extensive methods, anonymous types, dynamics, etc)
Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.
C#,.NET,Architect,Intermediate,VS2010,.Net,Articles,Computer Tutorials,LINQ,Database,Joins,LINQ Joins,SQL Joins