Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Sep 05, 2006 09:26 PM by synced
Aug 25, 2006 06:00 PM|LINK
Well, the first thing that comes to mind is that a DataContext might not be serializable. I talked to the LINQ team about "tear offs", or serializability, and they agreed that it was a scenario but didn't have time to make it work in the May LINQ Preview.
The best place to get information on DataContext serializability is the
LINQ forum. The LINQ team monitors it and will answer questions and take requests for features.
Sorry I can't help you more. I hope the LINQ team can help.
Aug 27, 2006 06:46 PM|LINK
I have been following DLinq/BLinq dev evolution. AFAIK, its not intended to work natively with Oracle, MySql or other DB but SqlServer. Is it true?
So after releasing the final version (any idea when it would be?), will it be others providers job to make this link between Linq and DB tech?
Aug 28, 2006 04:50 PM|LINK
Hope you had a good weekend!
Thanks for the reply Polita.
I can understand not everything works yet in the CTP's, that is fine.
I also have some questions as I have been previewing a lot of the CTP's as of lately. We are a web shop deciding if we want to switch to ASP.NET and these CTP's are giving us great insight into if we will make the switch or not.
From what I understand BLINQ does 2 things:
1. Created classes that are bound to your DB so you can use OO for data access
2. Auto-generate listing/insert/update/delete pages based off all of the generated classes in #1.
So I have been starting to take a look at ADO.NET vNext CTP. What I am concerned is having seperate data layers half being the auto-generated BLINQ ones, and then using ADO.NET vNext for other things. Is it possible later versions of BLINQ will be using
vNext for its objects rather than custom codegen classes?
I really like the wizards ADO.NET vNext has, but I also really like what BLINQ has to offer with auto-generated pages. I really don't want to have 2 seperate OO data layers to work with on one site.
Any insight on what the future holds would be great for our understanding of how things piece together. We have no problem waiting for things to mesh together in the CTP's but any insight on how all the pieces relate would be great.
So far ASP.NET's new technology CTP's have us very interested, great work :)
Aug 29, 2006 12:34 AM|LINK
The May LINQ Preview supports only SQL Server. However, other providers will be supported when LINQ is released.
Sep 05, 2006 07:56 PM|LINK
Can you please comment on my questions above? I am still concerned about having 2 branches of my data model created as objects for me and dealing with 2 API etc.
Thanks and take care.
Sep 05, 2006 08:11 PM|LINK
Sep 05, 2006 09:26 PM|LINK
Hmm I see. I thought ADO.NET vNext was an actual product update? I just sort of see a bit of overlap where both ADO.NET vNext and BLINQ generate objects to access your DB. So if I am going to use BLINQ along with the next iteration of ADO.NET then I am
going to have 2 seperate versions of my DB generated into classes, with different API.
Honestly feel that I am getting confused by Microsoft blurring the lines too much. I love the power BLINQ has for auto-generating pages, but both BLINQ and ADO.NET vNext generate an object structure of your DB and if some components use ADO.NET vNext, and
BLINQ doesn't use ADO.NET vNext objects, then I am basically forced to use both. Which seems like overkill to me.
It could be I am just confused as well, very possible :) I am just concerned of having my DB generated twice and using 2 seperate API etc. Very confusing!
Thanks for all your help throughout.