EF Reverse Engineering can't handle " #" in column name.

Question

EF Reverse Engineering can't handle " #" in column name.

Bill Duffy 0

I have a database that uses two different fields:

string "Asset
int "Asset #"

After running EF Reverse Engineering on the existing database, it creates a model with:

        [Column("Asset")]
        public string Asset { get; set; }
        [Column("Asset #")]
        public int Asset { get; set; }

This causes compile errors and fails to build. In this case I am running a secondary script that edits the resulting files and changes "int Asset" to "int AssetNum", which is a hack at best.

Is there another method within EF I can use to fix this?

Wenbin Geng 736 Reputation points Microsoft External Staff

2023-12-11T10:45:01.8933333+00:00
I tried to create the following table in the sqlserver database:

And the following entity classes were generated through dbfirst:

public string? Asset { get; set; } public int? Asset1 { get; set; } public int Id { get; set; }

If it is really inconvenient for you to modify your database name, you can also configure the column name by using HasColumnName ("name of column in database") in DbContext's Fluent API:

entity.Property(e => e.Asset) .HasMaxLength(10) .IsFixedLength().HasColumnName("Asset"); entity.Property(e => e.Asset1).HasColumnName("Asset #");

Your answer

Wenbin Geng 736 Reputation points Microsoft External Staff

2023-12-11T10:45:01.8933333+00:00

I tried to create the following table in the sqlserver database:

And the following entity classes were generated through dbfirst:

public string? Asset { get; set; } public int? Asset1 { get; set; } public int Id { get; set; }

If it is really inconvenient for you to modify your database name, you can also configure the column name by using HasColumnName ("name of column in database") in DbContext's Fluent API:

entity.Property(e => e.Asset) .HasMaxLength(10) .IsFixedLength().HasColumnName("Asset"); entity.Property(e => e.Asset1).HasColumnName("Asset #");

Share via

EF Reverse Engineering can't handle " #" in column name.

Your answer