Building Web Apps with ASP.NET Jump Start: (04) Building a Service Layer with ASP.NET Web API
Mar 25, 2013 at 8:32 AM@ecrap Yes, you absolutely can.
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
@ecrap Yes, you absolutely can.
I am so happy to see that a bug reported to MS that they have closed as "can't duplicate" happened to Scott Gu on stage in front of thousands of people and is recorded and posted here on Channel 9.
OH, actually they changed it to resolved... in VS 11. Wait what?! This bug is a major productivity issue.
https://connect.microsoft.com/VisualStudio/feedback/details/665418/some-keyboard-keys-stop-working
Please, someone that cares about the quality of VS 2010 get this back ported and released as a hot fix or patch. I can deal with VS being slow and hanging for seconds every now and then... but stopping to respond to the keyboard and mouse clicks is not acceptable.
Where is the high quality WMV download?
BOb
MaurizioR wrote:Yes, it is an exiciting feature.
My concern is about the security trace: is it possibile to trace the current user application name ?
Normally we connect application to SQL using a unique trusted connection (windows authentication), but we are interested to log all db changes along with the current logged (application) user; otherwise we know the db changes but not who made them.
MS had a web cast on this... can't remember if it was on EntityFW or on LINQ to SQL... but the [main] differences as it explained them:
Linq to SQL
1. Only suports SQL Server
2. One to one mapping from Table to Object (although the Linq to SQL designer does seem to have inheritence stuff in it... so I'm not sure if this is 100% true.)
EnityFramework
1. Provider based data model to support multiple back ends.
2. An object (entity) can be mapped to multiple tables.
This tells me I need to be using the EntityFramework. Item 1 doesn't bother me since all of my projects are SQL server. But, I want to do DDD and it doesn't look like Linq to SQL is really designed for that.
So, I still don't understand why we (Microsoft) have both projects. I think the Linq to SQL should be dropped and all resources should be invested in the EntityFramework. It has better design goals and is a superset of Linq to SQL.
BOb
clintsinger wrote:First of all, fascinating project.
I do have a question though. Currently in VS 2008 Beta 2 there is a new item which is LINQ to SQL which creates a couple files including a mapping to the database which can be queried using LINQ. You also get a design surface that looks similar to the Entities Design Surface.
What are the differences between the two (ie, why do they both exist) and why would one use one or the other?