Using NHibernate Restrictions without strings in the property name

When you create a criteria, you can add Restrictions that apply to a property. There are 2 ways of creating a Restriction:

Restrictions.Eq(string propertyName, object value)

or

Restrictions.Eq(IProjection 开发者_如何学运维projection, object value)

Thing is, I don't feel comfortable passing property names as strings, since if they ever change, my project will compile as usual and any possible naming mismatch will only be found during unit testing. I'm trying to implement TDD but it won't happen anytime soon, so I'm trying to limit dependencies of unit testing to check for errors (until we manage to embrace TDD).

Any ideas? Thanks in advance!

Use LINQ, QueryOver (NH3.x) or NH Lambda Extensions (NH2.x) or NHibernate Expression Extensions (NH1.2)

All of these are more strongly-typed than just using strings.

I can feel your pain.

But there is no way to put dynamic reference to your properties using projections in criteria API, just like you can't make nHibernate mapping detect a table or column name change.

Doing a find and replace step by step with "Property" with work in most cases.

As long as you have complete coverage of unit tests (you don't you?) it shouldn't be a problem, should it :-)?

Another reason to avoid using strings for property names is that refactoring using e.g. Resharper cannot fix those references. This is where Fluent NHibernate really shines.