Well, you might have got the idea!
Yes, I am on the LINQ bandwagon. I tuned into http://www.aspalliance.com/ and touched up on the LINQ articles by Scott Gu. They are really informative and I did get a very clear idea on what the other geeks are talking about (ooohhooo... that LINQ thing...its so cool, you know...). Now I know :-)
My only interest was how to use LINQ with Stored Procedures. And my concern is that we would need a paradigm shift in coding and architecture approach if we start using LINQ in our current applications. DataContext, you see... DataContext is the back bone of LINQ.
Subscribe to:
Post Comments (Atom)
Cookies, anyone?
Our application started having integration issues early March this year. Did I say that was intermittent? To add to our confusion, we coul...
-
Disclaimer: This post has nothing to do with washing or repairing cars. Well, I have been pondering over Managers and Management for lo...
-
I have been searching all over the place and talking to people regarding any issues faced during migrating the existing VS.NEt 2003 projects...
-
I have been busy lately with my day job, my side projects (some hobby and some real ones) and the user group activities. I haven't blogg...
I agree with you Rajeev. It needs a paradigm shift to tune to the LINQ methodology and I have a feel that it wouldn't be feasible on all architecture models, even though some argue that it would. Think about the latest MVC framework from Scott Gu team, looks cool but again not applicable with all the current architecture models.
ReplyDelete- Askar
Yes, I checked the Dynamic Data using the MVC framework. See my latest post.
ReplyDelete