How can I instruct SqlMetal to exclude the 'storage' attribute of all the columns on a mapping file when converting a .dbml file to a mapping file?

Question

Hi,
I'm trying to use LINQ to SQL with a top down approch using my own POCO classes. I'm using a XML file for the external mapping but in order to avoid typing a long file by hand I found that I could use the O/R designer to create the .dbml and from there I
could use SqlMetal.exe to generate the map file from the .dbml. The only thing is that, by default, SqlMetal generates a map file which includes the 'storage' attribute for all the columns of the database. For example:
<
Column
Name="Ticker"
Member="Ticker"
Storage="_Ticker"
DbType="NChar(20)
NOT NULL"
CanBeNull="false"
/>
However, in my code I only use automatic properties (Ticker, in this example) and not properties with the corresponding private field. Basically, I don't have any field "_Ticker" in my class. I found out that this the reason why I'm getting the error
"Bad Storage property: '_Ticker' on member 'TTS.Domain.Asset.Ticker" when trying to add an entity to the database. However, ff I delete the all the 'storage' attributes from my mapping file everything works fine.
Is there a way so I could use SqlMetal to generate a map file from a .dbml file but in which it never includes the 'storage' attribute?
Thanks.
Best,
Miguel T.
This is reason why I'm getting the error.

Answer 1

Hi Serguey,
I was expecting that answer but I still had some hope that it could be possible! I checked those 2 links before sending my question.
Currently, I'm deleting the storage attributes everytime that I generate a mapping file. The issue is that I will have to do this eveytime that I need to add data in my O/R designer which happens quite frequently since I'm working with iterations in my project.
It's not very practical but it's still better than write the additional data by hand.
I don't know how I could create my own mapping validation in order to exclude the 'storage' attributes everytime that I generate a mapping file from a .dbml file with SqlMetal but I will check that option too.
Thanks for your helps.
Best,
Miguel.