2/22/2025 9:00:18 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of .NET Extensions in SalesLogix version 7 and higher. View the code of conduct for posting guidelines.
|
|
|
|
Strong typed dataset in extension?
Posted: 15 Aug 08 1:34 PM
|
Has anyone ever successfully created a strong typed dataset in a .NET extension? I'm using VS 2008 and I can't use the XSD designer to create a strong typed dataset when I specify the SLX provider in the Server Explorer. When I use the SQL connection, it still doesn't work right.
Anyone had success with this? Any gotchas I might be missing?
Thanks,
Jeff
|
|
|
|
Re: Strong typed dataset in extension?
Posted: 26 Aug 08 7:14 AM
|
Hey Jeff,
On the DataSet side I do not really go down that Avenue since I am really an objects guy and since there is now such great data binding support for objects I really have shy'd away from that direction. That being said your problem may be more to do with the schema that Saleslogix provides. What I mean by that is there is not DB level defined primary/foreign keys and relationships in there underlying database tables. You might be able to point a SQL connection at the database and get what you need as well? I know with EntityFramework there is some difficulity because of the lack of keys/relationships (looks flat).
Just some thoughts,
Mark |
|
|
|
Re: Strong typed dataset in extension?
Posted: 26 Aug 08 10:06 AM
|
Thanks for the input, Mark. Hindsight being the good vision it is, I shouldn't have gone down the strong typed data set road. The initial problem I had was attempting to create the XSD - the provider (assuming it's the provider as when I changed to SQL it worked) kept throwing errors when I attempted to drag more than one table on to the designer. Finally just switched to sql for the provider - I rolled my own data access anyway. So all I really got were a lot of headaches and some column names that I defined and datatables, etc. I did add my own relationships (via the designer) and that worked OK, but that wasn't worth it.
I remember the last time I used the xsd's, I said never again. Apparently I was dumb enough to think it was a good fit this time, too. 
While I can't use LINQ in this project (I can't be guaranteed the users will have the 3.5 framework), I have seen a TON of uses for it - beyond the LINQ to SQL. I can see so many uses for the select from my objects to find data for validation, quick filtering, etc. that I really wish I could have used it.
As I was searching for something on datasets, I read someone's comment that strong typed datasets are the "poor man's data access layer". Couldn't agree more - and I still had to build so much, it was more trouble than it's worth.
Thanks for your thoughts.
Jeff
|
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|