Why do we add properties of model in ApplicationDbContext class that is generated by the visual studio
up vote
0
down vote
favorite
I was going through a tutorial and found something like this.
couldn't find out why the properties of a model class (i.e., Customers,Movies,..) are added to this context class that is auto-generated in the ASP.net MVC individual authentication template.
public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
{
public DbSet<Customer> Customers { get; set; }
public DbSet<Movie> Movies { get; set; }
public DbSet<MembershipType> MembershipTypes { get; set; }
public ApplicationDbContext()
: base("DefaultConnection", throwIfV1Schema: false)
{
}
public static ApplicationDbContext Create()
{
return new ApplicationDbContext();
}
}
c# entity-framework
|
show 1 more comment
up vote
0
down vote
favorite
I was going through a tutorial and found something like this.
couldn't find out why the properties of a model class (i.e., Customers,Movies,..) are added to this context class that is auto-generated in the ASP.net MVC individual authentication template.
public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
{
public DbSet<Customer> Customers { get; set; }
public DbSet<Movie> Movies { get; set; }
public DbSet<MembershipType> MembershipTypes { get; set; }
public ApplicationDbContext()
: base("DefaultConnection", throwIfV1Schema: false)
{
}
public static ApplicationDbContext Create()
{
return new ApplicationDbContext();
}
}
c# entity-framework
DbSet<Entity>
is a class form EntityFramework that represents a entity or a table in a database and theCustomers, Movies..
are the names of these tables.
– Llazar
Nov 21 at 17:54
1
To expand a bit on what @Llazar said, imagine you have 1000 models in your application. Not all of these models will need to have corresponding database tables but are instead only used to logically group together some data. Defining DbSets gives you a way of telling EntityFramework which classes/entities should be used to interact with the DB. This explanation is oversimplified by quite a bit- just trying to give a relate-able example that may help you
– GregH
Nov 21 at 18:36
How else would you access any of the classes in the database?
– BJ Myers
Nov 21 at 19:31
auto-generated - Well, there's always a source for auto-generation. We don't know that source so it's kinda hard to answer this.
– Gert Arnold
Nov 21 at 20:54
But my doubt is regarding whyDbSet
has been added to thisApplicationDbContext
which is dealing with the identity authorization.
– Madhuri Adhikarla
Nov 22 at 3:33
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was going through a tutorial and found something like this.
couldn't find out why the properties of a model class (i.e., Customers,Movies,..) are added to this context class that is auto-generated in the ASP.net MVC individual authentication template.
public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
{
public DbSet<Customer> Customers { get; set; }
public DbSet<Movie> Movies { get; set; }
public DbSet<MembershipType> MembershipTypes { get; set; }
public ApplicationDbContext()
: base("DefaultConnection", throwIfV1Schema: false)
{
}
public static ApplicationDbContext Create()
{
return new ApplicationDbContext();
}
}
c# entity-framework
I was going through a tutorial and found something like this.
couldn't find out why the properties of a model class (i.e., Customers,Movies,..) are added to this context class that is auto-generated in the ASP.net MVC individual authentication template.
public class ApplicationDbContext : IdentityDbContext<ApplicationUser>
{
public DbSet<Customer> Customers { get; set; }
public DbSet<Movie> Movies { get; set; }
public DbSet<MembershipType> MembershipTypes { get; set; }
public ApplicationDbContext()
: base("DefaultConnection", throwIfV1Schema: false)
{
}
public static ApplicationDbContext Create()
{
return new ApplicationDbContext();
}
}
c# entity-framework
c# entity-framework
edited Nov 21 at 20:49
user3559349
asked Nov 21 at 17:47
Madhuri Adhikarla
45
45
DbSet<Entity>
is a class form EntityFramework that represents a entity or a table in a database and theCustomers, Movies..
are the names of these tables.
– Llazar
Nov 21 at 17:54
1
To expand a bit on what @Llazar said, imagine you have 1000 models in your application. Not all of these models will need to have corresponding database tables but are instead only used to logically group together some data. Defining DbSets gives you a way of telling EntityFramework which classes/entities should be used to interact with the DB. This explanation is oversimplified by quite a bit- just trying to give a relate-able example that may help you
– GregH
Nov 21 at 18:36
How else would you access any of the classes in the database?
– BJ Myers
Nov 21 at 19:31
auto-generated - Well, there's always a source for auto-generation. We don't know that source so it's kinda hard to answer this.
– Gert Arnold
Nov 21 at 20:54
But my doubt is regarding whyDbSet
has been added to thisApplicationDbContext
which is dealing with the identity authorization.
– Madhuri Adhikarla
Nov 22 at 3:33
|
show 1 more comment
DbSet<Entity>
is a class form EntityFramework that represents a entity or a table in a database and theCustomers, Movies..
are the names of these tables.
– Llazar
Nov 21 at 17:54
1
To expand a bit on what @Llazar said, imagine you have 1000 models in your application. Not all of these models will need to have corresponding database tables but are instead only used to logically group together some data. Defining DbSets gives you a way of telling EntityFramework which classes/entities should be used to interact with the DB. This explanation is oversimplified by quite a bit- just trying to give a relate-able example that may help you
– GregH
Nov 21 at 18:36
How else would you access any of the classes in the database?
– BJ Myers
Nov 21 at 19:31
auto-generated - Well, there's always a source for auto-generation. We don't know that source so it's kinda hard to answer this.
– Gert Arnold
Nov 21 at 20:54
But my doubt is regarding whyDbSet
has been added to thisApplicationDbContext
which is dealing with the identity authorization.
– Madhuri Adhikarla
Nov 22 at 3:33
DbSet<Entity>
is a class form EntityFramework that represents a entity or a table in a database and the Customers, Movies..
are the names of these tables.– Llazar
Nov 21 at 17:54
DbSet<Entity>
is a class form EntityFramework that represents a entity or a table in a database and the Customers, Movies..
are the names of these tables.– Llazar
Nov 21 at 17:54
1
1
To expand a bit on what @Llazar said, imagine you have 1000 models in your application. Not all of these models will need to have corresponding database tables but are instead only used to logically group together some data. Defining DbSets gives you a way of telling EntityFramework which classes/entities should be used to interact with the DB. This explanation is oversimplified by quite a bit- just trying to give a relate-able example that may help you
– GregH
Nov 21 at 18:36
To expand a bit on what @Llazar said, imagine you have 1000 models in your application. Not all of these models will need to have corresponding database tables but are instead only used to logically group together some data. Defining DbSets gives you a way of telling EntityFramework which classes/entities should be used to interact with the DB. This explanation is oversimplified by quite a bit- just trying to give a relate-able example that may help you
– GregH
Nov 21 at 18:36
How else would you access any of the classes in the database?
– BJ Myers
Nov 21 at 19:31
How else would you access any of the classes in the database?
– BJ Myers
Nov 21 at 19:31
auto-generated - Well, there's always a source for auto-generation. We don't know that source so it's kinda hard to answer this.
– Gert Arnold
Nov 21 at 20:54
auto-generated - Well, there's always a source for auto-generation. We don't know that source so it's kinda hard to answer this.
– Gert Arnold
Nov 21 at 20:54
But my doubt is regarding why
DbSet
has been added to this ApplicationDbContext
which is dealing with the identity authorization.– Madhuri Adhikarla
Nov 22 at 3:33
But my doubt is regarding why
DbSet
has been added to this ApplicationDbContext
which is dealing with the identity authorization.– Madhuri Adhikarla
Nov 22 at 3:33
|
show 1 more comment
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53417871%2fwhy-do-we-add-properties-of-model-in-applicationdbcontext-class-that-is-generate%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
DbSet<Entity>
is a class form EntityFramework that represents a entity or a table in a database and theCustomers, Movies..
are the names of these tables.– Llazar
Nov 21 at 17:54
1
To expand a bit on what @Llazar said, imagine you have 1000 models in your application. Not all of these models will need to have corresponding database tables but are instead only used to logically group together some data. Defining DbSets gives you a way of telling EntityFramework which classes/entities should be used to interact with the DB. This explanation is oversimplified by quite a bit- just trying to give a relate-able example that may help you
– GregH
Nov 21 at 18:36
How else would you access any of the classes in the database?
– BJ Myers
Nov 21 at 19:31
auto-generated - Well, there's always a source for auto-generation. We don't know that source so it's kinda hard to answer this.
– Gert Arnold
Nov 21 at 20:54
But my doubt is regarding why
DbSet
has been added to thisApplicationDbContext
which is dealing with the identity authorization.– Madhuri Adhikarla
Nov 22 at 3:33