http://blogs.msdn.com/b/alexj/archive/2010/02/12/tip-53-how-to-debug-ef-poco-mapping-issues.aspxIf you are trying to use POCO classes in EF 4.0, it is relatively easy to run into problems with the mapping from your model to your CLR classes. If you get any nasty problems here, the best way to get to the bottom of things is to try to explicitlyen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/alexj/archive/2010/02/12/tip-53-how-to-debug-ef-poco-mapping-issues.aspx#9971865Tue, 02 Mar 2010 23:52:05 GMT91d46819-8472-40ad-a661-2c78acb4018c:9971865Alex D James<p>Zeeshan, </p> <p>Sounds like an EF bug. As you (but others reading this don't) the EF team now has a bug tracking this.</p> <p>Alex</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9971865" width="1" height="1">http://blogs.msdn.com/b/alexj/archive/2010/02/12/tip-53-how-to-debug-ef-poco-mapping-issues.aspx#9971648Tue, 02 Mar 2010 17:49:44 GMT91d46819-8472-40ad-a661-2c78acb4018c:9971648Zeeshan Hirani<p>Hey Alex,</p> <p>This does not work if you have in correct data type only works when you have a property missing. Seems like it does not do complete vaidation until very later. like on my model i had the cost defined as Decimal but on the class i changed it string and it passed this process easily.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9971648" width="1" height="1">