Support specifying a default value for a column corresponding to an enum model property

[eriksendc]

Hi All,

I have an enum as follows:

public enum FirstTimeSignInDestination { Unknown = 0, Homepage = 1, GuardianDashboard = 2, Search = 3, AdopterDashboard = 4 }

In the OnModelCreating() override of my DbContext-derived class I put the following:

builder.Entity<ApplicationUser>().Property(p => p.FirstTimeSignInDestination). HasDefaultValue(FirstTimeSignInDestination.Unknown);

This compiles, but when I do dnx ef migrations add FirstTimeSignInDestination I get the following error message:

Annotations of type 'FirstTimeSignInDestination' are not supported. Only common simple .NET types are currently supported.

Since I know FirstTimeSignInDestination.Unknown corresponds to 0 I just used 0 instead and everything works. It would be cool for this to work with one of the enum values as I'd tried, though.

Thanks for your consideration.

Regards,
-Brian Eriksen

[rykr]

@rowanmiller

I have a similar issue. if I have an enum like this:

public enum MyEnum:int { ValA = 1, ValB = 2, ValC = 4 }

And then I specify an entity property like this:

public class BlahBlah {
.....
[DefaultValue(MyEnum.ValA)]
public MyEnum EnumVal { get; set; }
...
}

When that is generted, the "Up" migration method will add the EnumVal column and give it a default value of MyEnum.0. This doesn't compile and is not even a valid scalar value for the enum.

Is enum default values not supported? If this can be handled, how should I handle it?

[rowanmiller]

Default enum values are not really supported yet (this issue is tracking that). The best way to handle it at the moment is to specify the default as the underlying type (i.e. 1 rather than MyEnum.ValA).

[rykr]

Thanks. We'll do that and hopefully this will be supported in the future.

[bricelam]

@smitpatel Do you know if this works now?