…ying to get the SessionFactoryAttribute attached to this, instead of the entity being passed in
…ations more appropriately and allows for a WCF implementation of multiple database sessions.
…t now contains a link to the online documentation.
…dated the respective assembly in the VS project template as well.
…ry.txt for the latest details.
…a patch from http://code.google.com/p/sharp-architecture/issues/detail?id=94 (thanks Hedgic!)
…otected to resolve http://code.google.com/p/sharp-architecture/issues/detail?id=99 . Had to change the visibility of this overridden method within Order.cs, accordingly.
…iberate to SharpArch.Testing.NHibernate to fix http://code.google.com/p/sharp-architecture/issues/detail?id=100
…s 2.5 approach to doing this, described at http://mint.litemedia.se/2009/05/30/new-expectedexception-model-in-nunit-25/. Also updated a couple of version references within csproj files.
…2.1 Beta 1, Fluent NHibernate, NHibernate Validator, LINQ to NHibernate, Json.NET 3.5 Beta 3, and Castle Windsor 2.0. Signed SharpArch.WcfClient.Castle.csproj.
…o be 31 based on information found at http://computinglife.wordpress.com/2008/11/20/why-do-hash-functions-use-prime-numbers/ and other sources. Modified Entity.cs to include the object's type in the hashcode calculation, in addition to its Id, for persistent objects. Added a couple of tests to prove all of this working, including one using LINQ's Intersect with BaseObjectEqualityComparer.cs.
When the entity is transient the hashcode is computed based on the domain signature and cached. Therefore during the lifetime of the object (not that of the entity) the hashcode cannot change even if domain signature changes or the object becomes persistent. When the object is persistent the hashcode is that of its Id, so that, it's unchanged forever. * Some minor refactorings
… for comparing BaseObject objects or anything that derives from BaseObject.
… return true so that the MVC binder won't add "A value is required." error to ModelState if, e.g., a drop down of int values is not selected. This way, it leaves it up to the application's validation layer to determine if the action is allowable or not.