Visual Studio Toolbox: Entity Framework Part 2
- Posted: Jan 25, 2012 at 8:01 AM
- 40,000 Views
- 12 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- High Quality WMV (PC, Xbox, MCE)
- MP3 (Audio only)
- Mid Quality WMV (Lo-band, Mobile)
- High Quality MP4 (iPad, PC)
- MP4 (iPod, Zune HD)
- Mid Quality MP4 (WP7, HTML5)
In this episode, Rowan Miller and Diego Vega return for Part 2 of our deep dive into the Entity Framework. In Part 1, they showed the following workflows available in Entity Framework 4.2: Code First, Model First, Database First, and Code First with an existing database. In this episode, they show a new feature coming very soon in version 4.3: Code First Migrations. And then they talk about what's coming in Entity Framework 5.0.
- Code First Migrations starts around 3:40
- Entity Framework futures starts around 25:20
Comment on the Post
Already have a Channel 9 account? Please sign in
Follow the Discussion
Interesting video and thank you.
I however see different data in terms of Linq to SQL usage over Linq to Entities in the field. Primarily because Linq to Entities has some problems on Windows XP and that is a large platform in the deployment area, specifically for line of business and enterprise software. Its also quicker out of the box to knock out a Linq to SQL classes model and start coding right away, without the worry about how to handle the metadata files that are intrinsic to Linq to Entities.
Despite all of this, I agree that Linq to Entities is the way to go in the long run. I use it in many of my products and services to support multiple database models (primary SQL Server and MySQL).
Keep up the hard work and will look forward to more videos to come.
@Everyone: Here is a link to the EF 4.3 beta release announcement. You will find more information about what is included and how to get the bits: http://blogs.msdn.com/b/adonet/archive/2012/01/12/ef-4-3-beta-1-released.aspx.
Thanks.
I do have one question regarding future releases,
If EF will be NuGet only, what will support for Express versions be seeing as NuGet is an extension; or will it be (or is it) one of the few Express scantioned extensions? Obviously if NuGet isn't usable in Express this will severly limit who can use the latest versions.
@Atlantisbase: NuGet will be available in all SKUs of Visual Studio 11. Unfortunately I don't think there is a way to get NuGet to install in Visual C# Express 2010 or Visual Basic Express 2010, but here is a workaround:
This should give you access to all the functionality of DbContext and CodeFirst. I am not sure there is a way to manually register the Migrations scripts in Visual Studio though.
Interesting new features but Robert needs to speak to Scott Hanselman about presentation skills.
@PhilMurray:How about I talk to you?
What should I do to improve my presentation skills? Be honest, but nice.
I didn't think there was any poor presentation skills here. I think the gentlemen in the middle (Diego I believe) could have been a little bit more involved through the beginning, but it was a good video and educational nonetheless.
Hey EF team! I have a question that has been driving me and others nuts, because a solution is not easy to find on the net. What is the best way to output metadata files for multiple types of databases to file (or embedded).
For example, I have a EF model that defines my database schema. The same model is used for both MySQL and SQL Server. The current way we have dealt with this is to change the DDL Generation Template property between SSDLToSQL10.tt and SSDLToMySQL.tt and build each one to get the appropriate output, then load them from the file system in our app.
This has to be done manually for each database type we support. So we have to do a build for SQL, and a build for MySQL. Is there a better way to automate this process so we don't have to manually edit the model in Visual Studio causing a checkout from source control and to prevent breaking the model? It would be best if these changes did not have to be made manually each time.
Great video! statement completion in the package manager console (as shown in the video) doesn't work for me, at least not with the usual Ctrl+Spacebar am I doing it wrong?
Chenel-9
Thanks
For your Program
Awesome series and great job by all - got me to look back to EF as a real option once again.
It was good that the episodes were actually longer than usual and being an Aussie I found Rowan very easy to listen to. Diego (sorry if it is not right) had a harder accent for me but a very smart and reserved guy. And Robert, well great as always, keeping it focused but asking questions that most of us would have too - great host on a valuable and informative show.
Keep up the good work and +1 for more of these "meaty" shows rather than video reviews of products. Thanks guys!
ps: didnt understand the logic of going to EF 5 rather than EF 4.5 as a numbering, as it contradicted the reasons for the team going straight from EF1 / 2 straight to EF4
Nice! Thank you Robert. Bring them back please.
Remove this comment
Remove this thread
close