Hi Fabio and Kevin, thanks for your reply.
Does this mean that , say I am using a non Sql Server database, LINQ is of no use ??. Or can I use Linq with Objects , and if so, How would I get stuff Into the Object, then use Linq, and then get stuff out of the object and back into my database.
.....it is highly probable that other database vendors will come up with their specific implementations
One ot the things I have noticed with .net, is that you cannot really use it in a stand alone basis. I keep coming up with Problems all the time, that simply cannot be done in .net....I find this very surprising for the premier development tool from Microsoft.
The most recent issuse I had was in an ASP.net web form. I was trying to set up a Grid which could be navigated in a simple fashion using up and down arrow keys...This is a requirement I have used in almost every application I have ever developed...simple enough I thought...Visual Studio.net to the rescue...afraid not...it just cannot do this out of the box...I eventually ended up purchasing a product call Spread from Farpoint which does a good job at , IMHO, is a very basic requirement.
Regards,
Gerard
>Hi Gerard,
>
>As Kevin had pointerd out, Linq to SQL is currently exclusive to Microsoft SQL Server. Despite of that, the Linq to SQL extensibility model allows developers to extend Linq to SQL so that they can support other database engines. IMHO, it is highly probable that other database vendors will come up with their specific implementations for Linq to SQL in the future.
>
>You can assess Linq to SQL extensibility model by checking some of the projects that are coming up from the community these days. They are not necessarily implementations for Linq to SQL, but they use the underlying extensibility model to do their job:
>
>
>
>HTH.
