ship simulator extremes mods free downloadpower quest drive image 2002 downloadpersonal medical history template downloadoffice 10 free download with crack
last updated October 22, 2015
The Contoso University sample web application demonstrates how to make MVC 5 applications with all the Entity Framework 6 and Visual Studio 2013. This tutorial uses the Code First workflow. For information about how to select from Code First, Database First, and Model First, see Entity Framework Development Workflows.
The sample application is often a web site for just a fictional Contoso University. It includes functionality including student admission, course creation, and instructor assignments. This tutorial series explains how to construct the Contoso University sample application. You can download the completed application.
A Visual Basic version translated by Mike Brind is obtainable: MVC 5 with EF 6 in Visual Basic around the Mikesdotnetting site.
Entity Framework 6 EntityFramework 6.1.0 NuGet package
Please leave feedback on what you liked this tutorial and what we should could improve inside the comments in the bottom of the page. If you have questions that aren't directly related towards the tutorial, you'll be able to post them for the Entity Framework forum, the Entity Framework and LINQ to Entities forum, or
If you have into a problem you cant resolve, you'll be able to generally discover the solution on the problem by comparing your code towards the completed project that you may download. For some common errors and ways to solve them, see Common errors, and solutions or workarounds for the kids.
The application the information building over these tutorials is usually a simple university website.
Users can look at and update student, course, and instructor information. Here are a few with the screens youll create.
The UI type of this site may be kept near to whats generated through the built-in templates, so the tutorial can focus mainly regarding how to utilize Entity Framework.
See Software Versions at the top on the page. Entity Framework 6 will not be a prerequisite simply because you install the EF NuGet package as part on the tutorial.
Open Visual Studio and make up a new C Web project named ContosoUniversity.
If the Host inside cloud check box inside the Microsoft Azure section is selected, clear it.
In the Change Authentication dialog box, select No Authentication, and click OK. For this tutorial you won t be requiring users to go browsing or restricting access according to who s logged on.
Back inside New Project dialog box, click OK to generate the project.
A few simple changes sets up the web page menu, layout, and website.
Open, to make the following changes:
Change each occurrence of My Application and Application name to Contoso University.
Add menu entries for Students, Courses, Instructors, and Departments, and delete the Contact entry.
The changes are highlighted.
In, replace the contents in the file with these code to change the text about and MVC with text relating to this application:
Home Page; div classjumbotron h1 Contoso University/h1 /div div classrow div classcol-md-4 h2 Welcome to Contoso University/h2 p Contoso University is really a sample application that demonstrates how make use of Entity Framework 6 inside an MVC 5 web application./p /div div classcol-md-4 h2 Build it from scratch/h2 p You can build the appliance by following the steps within the tutorial series around the site./p p a classbtn btn-default /mvc/tutorials/getting-started-with-ef-using-mvc/See the tutorial raquo;/a /p /div div classcol-md-4 h2 Download it/h2 p You can download the completed project in the Microsoft Code Gallery./p p a classbtn btn-default /ASPNET-MVC-Application-b01a9fe8 Download raquo;/a /p /div /div
Press CTRLF5 to operate the site. You see the home-page with the main menu.
The image shows 6.0.0 being installed, but NuGet will install the most recent version of Entity Framework excluding pre-release versions, which as from the most recent update to your tutorial is 6.1.1.
This step is truly one of a few steps that it tutorial has you are doing manually, but which often can have been done automatically through the MVC scaffolding feature. Youre doing them manually so that you may see the steps required to utilize Entity Framework. Youll use scaffolding later to generate the MVC controller and views. An alternative would be to let scaffolding automatically install the EF NuGet package, make the database context class, and make the connection string. When youre prepared to do it this way, all you have to do is skip those steps and scaffold your MVC controller when you create your entity classes.
Next youll create entity classes to the Contoso University application. Youll start with this three entities:
entities, and theres a one-to-many relationship between
entities. In other words, each student can be signed up for any number of courses, as well as a course can have many students opted in for it.
In this sections youll build a class for every single one of these entities.
Note If you try to compile the project prior to finish creating many of these entity classes, youll get compiler errors.
In the Models folder, build a class file named and replace web site code with the subsequent code:
using System; using ; namespace public class Student public int ID get; set; public string LastName get; set; public string FirstMidName get; set; public DateTime EnrollmentDate get; set; public virtual ICollection Enrollment Enrollments get; set;
property can be the primary key column from the database table that corresponds to the present class. By default, the Entity Framework interprets a house thats named
property is often a navigation property. Navigation properties hold other entities which might be related to this particular entity. In this case, the
entity. In other words, if your given
so that they may take advantage of certain Entity Framework functionality for example lazy loading. Lazy loading will likely be explained later, inside Reading Related Data tutorial later within this series.
If a navigation property holds multiple entities like many-to-many or one-to-many relationships, its type should be a list through which entries is usually added, deleted, and updated, for instance
In the Models folder, create and replace the current code with these code:
namespace public enum Grade A, B, C, D, F public class Enrollment public int EnrollmentID get; set; public int CourseID get; set; public int StudentID get; set; public Grade? Grade get; set; public virtual Course Course get; set; public virtual Student Student get; set;
property will be the key key; this entity uses the classname
entity. Ordinarily you should choose one pattern and then use it throughout important computer data model. Here, the variation illustrates that you are able to use either pattern. In a later tutorial, youll youll observe how using
makes less complicated to implement inheritance inside data model.
property is undoubtedly an enum. The question mark after the
property is nullable. A grade thats null differs from a zero grade null means a grade isnt known or hasnt been assigned yet.
property can be a foreign key, as well as the corresponding navigation property is
entity, therefore, the property could only hold a single
navigation property you saw earlier, which can take multiple
property is usually a foreign key, and also the corresponding navigation property is
Entity Framework interprets a home as a foreign key property whether named navigation property name primary key property reputable name example,
Foreign key properties will also be named exactly the same simply primary key property reputation for example,
In the Models folder, create , replacing web page . code with this code:
using ; using ; namespace public class Course public int CourseID get; set; public string Title get; set; public int Credits get; set; public virtual ICollection Enrollment Enrollments get; set;
property is often a navigation property. A
Well say more details on the DatabaseGenerated attribute within a later tutorial with this series. Basically, this attribute enables you to enter the main key with the course in lieu of having the database generate it.
The main class that coordinates Entity Framework functionality for any given data model would be the database context class. You create these kinds by deriving in the class. In your code you specify which entities are included from the data model. You can also customize certain Entity Framework behavior. In this project, the category is named
To build a folder inside the ContosoUniversity project, right-click the project in Solution Explorer and then click Add, and after that click New Folder. Name the revolutionary folder DAL for Data Access Layer. In that folder develop a new class file named, and replace web site code with these code:
using ; using ; using ; namespace public class SchoolContext: DbContext public SchoolContext: baseSchoolContext public DbSet Student Students get; set; public DbSet Enrollment Enrollments get; set; public DbSet Course Courses get; set; protected override void OnModelCreatingDbModelBuilder modelBuilder PluralizingTableNameConvention ;
This code produces a DbSet property for every entity set. In Entity Framework terminology, an entity set typically corresponds to some database table, with an entity corresponds with a row within the table.
statements and yes it would work the identical. The Entity Framework would come with them implicitly because the
The name on the connection string which youll add to your file later is passed in for the constructor.
You may possibly also pass within the connection string itself instead with the name of merely one that is stored from the file. For more information about methods of specifying the database to work with, see Entity Framework - Connections and Models.
If you dont specify appreciable link string or name of a single explicitly, Entity Framework assumes that the bond string name is precisely the same as the category name. The default connection string name in this particular example would then be
exactly the same as what youre specifying explicitly.
statement inside OnModelCreating method prevents table names from being pluralized. If you didnt try this, the generated tables inside the database could be named
Instead, the table names will likely be
Developers disagree about whether table names must be pluralized or otherwise not. This tutorial uses the singular form, nevertheless the important point is that you may select whichever form you like by including or omitting this distinctive line of code.
The Entity Framework can automatically create or drop and re-make a database in your case when the appliance runs. You can specify that it should be done whenever your application runs or only if the model no longer has sufficient sync with all the existing database. You can also write a
method which the Entity Framework automatically calls after creating the database so that you can populate it with test data.
The default behavior is to produce a database provided that it doesnt exist and throw different if the model has changed and also the database already exists. In this section youll specify which the database needs to be dropped and re-created whenever the model changes. Dropping the database causes the decline of all crucial computer data. This is generally OK during development, because the
method will run if your database is re-created and definately will re-you could make your test data. But in production you generally dont want to lose all important computer data every time you have to change the database schema. Later youll observe how to handle model changes by utilizing Code First Migrations to modify the database schema as an alternative to dropping and re-creating the database.
In the DAL folder, develop a new class file named and replace web page . code using the
following code, that can cause a database being created as needed and loads test data into the brand new database.
using System; using ; using ; using ; using ; using ; namespace public class SchoolInitializer: DropCreateDatabaseIfModelChanges SchoolContext protected override void SeedSchoolContext context var students new List Student new 2005-09-01, new 2002-09-01, new 2003-09-01, new 2002-09-01, new 2002-09-01, new 2001-09-01, new 2003-09-01, new 2005-09-01 ; s s; ; var courses new List Course new CourseCourseID1050, TitleChemistry, Credits3,, new CourseCourseID4022, TitleMicroeconomics, Credits3,, new CourseCourseID4041, TitleMacroeconomics, Credits3,, new CourseCourseID1045, TitleCalculus, Credits4,, new CourseCourseID3141, TitleTrigonometry, Credits4,, new CourseCourseID2021, TitleComposition, Credits3,, new CourseCourseID2042, TitleLiterature, Credits4, ; s s; ; var enrollments new List Enrollment new EnrollmentStudentID1, CourseID1050, GradeGrade.A, new EnrollmentStudentID1, CourseID4022, GradeGrade.C, new EnrollmentStudentID1, CourseID4041, GradeGrade.B, new EnrollmentStudentID2, CourseID1045, GradeGrade.B, new EnrollmentStudentID2, CourseID3141, GradeGrade.F, new EnrollmentStudentID2, CourseID2021, GradeGrade.F, new EnrollmentStudentID3, CourseID1050, new EnrollmentStudentID4, CourseID1050,, new EnrollmentStudentID4, CourseID4022, GradeGrade.F, new EnrollmentStudentID5, CourseID4041, GradeGrade.C, new EnrollmentStudentID6, CourseID1045, new EnrollmentStudentID7, CourseID3141, GradeGrade.A, ; s s; ;
method takes the database context object being an input parameter, and also the code from the method uses
that mind add new entities towards the database. For each entity type, the code generates a collection of new
entities, adds them on the appropriate
property, after which saves the changes to your database. It isnt
method after each gang of entities, as they are done here, but doing that helps
you locate the foundation of a problem if very occurs as the code is writing to your database.
To tell Entity Framework to make use of your initializer class, add an element for the
element inside application file the one within the root project folder, as shown from the following example:
contexts context, ContosoUniversity databaseInitializer, ContosoUniversity/context /contexts
defaultConnectionFactory, EntityFramework parameters parameter valuev11.0/parameters /defaultConnectionFactory providers provider , /providers /entityFramework
specifies the fully qualified context class name as well as the assembly its in, as well as the
specifies the fully qualified name with the initializer class along with the assembly its in. When you dont want EF to utilize initializer, you may set an attribute within the
application, the Entity Framework compares the database to your model your
and entity classes. If theres a difference, the application form drops and re-creates the database.
Note: When you deploy an application into a production web server, you should remove or disable code that drops and re-creates the database. Youll do that in a very later tutorial within this series.
LocalDB is often a lightweight version on the SQL Server Express Database Engine. Its easy to fit and configure, starts at will, and runs in user mode. LocalDB runs inside a special execution mode of SQL Server Express so that you to use databases as files. You can put LocalDB database files from the AppData folder of your web project if you want to get able to copy the database while using project. The user instance feature in SQL Server Express also enables someone to work with files, nevertheless the user instance feature is deprecated; therefore, LocalDB is usually recommended for utilizing files. In Visual Studio 2012 and later on versions, LocalDB is installed automagically with Visual Studio.
Typically SQL Server Express just sits there for production web applications. LocalDB particularly is not appropriate for production use which has a web application because it is just not designed to help IIS.
In this tutorial youll help LocalDB. Open the applying file and add a
element, as shown within the following example. Make sure you update the file within the root project folder. Theres fashionable file is inside Views subfolder that you just dont need to update.
If you're using Visual Studio 2015, replace v11.0 from the connection string with MSSQLLocalDB, because default SQL Server instance name has evolved.
connectionStrings add nameSchoolContext connectionStringData SourceLocalDbv11.0;Initial CatalogContosoUniversity1;Integrated SecuritySSPI; /connectionStrings
appSettings add keywebpages:Version value3.0.0.0 add keywebpages:Enabled valuefalse add keyClientValidationEnabled valuetrue add keyUnobtrusiveJavaScriptEnabled valuetrue/appSettings
The connection string you ve added specifies that Entity Framework makes use of a LocalDB database named. The database doesnt exist yet; EF can create it. If you wanted the database to become created with your AppData folder, you might add