Linq to SQL use the sql native client and NOT Ole DB
SalesLogix uses OLEDB to my knowledge there are no automated tools for creating linq to oledb classes like there are for linq to sql.
You have 2 options here basically.
1. Write your own DAL that leverages the OleDB Provider and implements linq or
2. Generate a linq to sql class, and then re-work it to use oledb. Keep inmind that all paramters generated buy the LinqToSQL tools generate named parameters and oledb DOES NOT USE named parameters.
I attempted Option 2 and soon realized I did not have the time or patience for this. So I created my own DAL that gets just the data I need.
There is a third option of creating your own LinqToOleDB genration tool. Again, I have neither the time nor the patience for this.
FYI if you are doing readonly calls to the SalesLogix Database and SalesLogix Security is NOT a concern then you can generate a linq to sql class using the sysdba credentials.
One remaining option which I rely quite heavily on is SData. I have a few production 3rd party tools 1 in MS Access, and 2 in C#.net that now use SData for communicating with the saleslogix database. This uses all of the security features of SalesLogix, all you have to do is write some repository classes that get the data you need. |