>>>>>>>>What is the optimum & most secure way to update data from within an application.
>>>>>>>>some use direct "Update" command, some do it through SQL stored procedure, ...
>>>>>>>>
>>>>>>>>The development tools used are VB.NET 2008 and SQL 2005
>>>>>>>
>>>>>>>For security you will want to use Stored Procedures - this way you are not exposing your database structure information,
>>>>>>
>>>>>>With the Entity framework as far as I understood everything is secure.
>>>>>
>>>>>I saw a presentation the other day, and was left with a big "So What?". It seems neat and everything, but I really didn't see too many advantages to a traditional ADO.NET approach. Granted, the presentation might not have been that good.
>>>>
>>>>There has been a lot of coverage of ADO.NET lately in the .NET course I am taking and I don't understand why some people say it's so hard to work with. It seems pretty straightforward, with lots of options if you want to use them.
>>>>
>>>>Don't know diddly about Entity Framework yet, other than that it is supposedly elbowing Linq out of the way within Microsoft.
>>>
>>>One of the 3-ways to work with the EF is LinQ to Entities, so I doubt that it is doing away with LinQ in MS.
>>
>>I didn't say doing away with it. Some signs I have seen indicate the EF will be Microsoft's strategic direction, though. You know how they have a tendency to jump from one flavor of the day to the next. Here is a post on the ADO.NET team's blog from the end of October, and a linq (sorry) to the full blog entry with comments ---
>>
>>Thank you for your comments. We apologize for the delay in response as we were at PDC this week, but wanted to get the post out in line with our PDC sessions. We would like to reiterate that we are listening to customers regarding LINQ to SQL and will continue to evolve the product based on feedback we receive from the community, but that as many of you said, we are making a significant investment in the Entity Framework and many other MS technologies are planning to build on the Entity Framework going forward.
>>
>>We would like to assure you that as we invest in the Entity Framework going forward, it is our priority to ensure it enables the same simple, lightweight usage scenario you currently have with LINQ to SQL and will continue to be fully compatible with newer MS technologies that are building on top of the Entity Framework down the road. For more information on some of the features we are working on to enable this scenario in the Entity Framework please check out the EFDesign Blog and PDC’s EF Futures from this past Tuesday.
>>
>>Elisa Flasko
>>
>>Program Manager, Data Programmability
>>
>>http://blogs.msdn.com/adonet/archive/2008/10/29/update-on-linq-to-sql-and-linq-to-entities-roadmap.aspx
>
>Hi,
>I think you need to distinguish between Linq in general and 'Linq to SQL'. It's just the latter that is supposedly being edged out by the entites framework.

Agreed.