I've used EntitySpaces templates to generate code for my database and noticed that columns with special characters are not encoded and causes compile errors. For example database columns
[Account%] [numeric](28, 2) NULL CONSTRAINT
[Account$] [numeric](28, 2) NULL CONSTRAINT
Generated to invalid
Public Const E-mail As String
virtual public System.Decimal? Account%
virtual public System.Decimal? Account$
It will be good to have standard functions to encode special characters and include them in most templates.
It could be similar to XmlConvert.EncodeName Method, that uses _xHHHH_ escaping.
See my blog post http://geekswithblogs.net/mnf/articles/101737.aspx
for an example of similar implementation.