Today I upgraded my project to FluentNHibernate 1.1. Ever since, when running my project I get the following exception:
Could not find a setter for property 'FullName' in class 'MyNamespace.Employee'
The code for the FullName property is as follows:
public virtual string FullName
{
get
{
return FirstName + " " + LastName;
}
}
Well yes, there is no setter indeed. But it used to work prior to version 1.1.
Now I know there are probably a few good arguments in the spritit of separation of concerns, for not implementing such calculated (non-persistent) property but let's just assume I'm doing the right thing here.
Why does FluentNHibernate suddenly require a setter for each property? I don't want to add one, it really wouldn't make sense in this case.
Perhaps there's something I can change to the conventions but I'm a bit puzzled here... I've read the v1.1 release notes but I couldn't find anything related to this problem.