problem in creation of nullable property in CodeFirst approach

Question

        .I created project with .net core 6. 
     GroupImageName is nullable but when I do migration, this property is created non-nullabe,also for example, posts property is created non-nullable.

what is the problem? How can I resolve it?

Please upload code in text instead in images. Images can't be searched and therefore aren't useful to future readers, harder to read than text. — Victor
– Victor, Commented Sep 14, 2022 at 10:28

Kiran Joshi · Accepted Answer · 2022-09-14 12:23:59Z

1

To make a nullable properties from code first you have to use Nullable<string> or string? which makes your property nullable in database after migration

E.g. in your case your model looks like below:

PostGroup.CS

Public class PostGroup
{
   public int GroupId{get;set;}
   public string GroupName {get;set;}
   public string? GroupImageName {get;set;}
   .
   .
   .
   n so on properties
}

after making above change just run the command like below from PMC

add-migration
update-database

above stapes will make your properties nullable in db after successful migration

edited Sep 14, 2022 at 12:23

answered Sep 14, 2022 at 12:17

Kiran Joshi

1,8763 gold badges15 silver badges36 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

problem in creation of nullable property in CodeFirst approach

what is the problem? How can I resolve it?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

what is the problem? How can I resolve it?

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related