Upgraded Castle ActiveRecord's NHibernate to 3.3.1.4000

[justintoth]

Not sure of the implications of this upgrade, but I was able to get the AR source compiling with the latest version of NHibernate. Everything seems to run fine in my applications with the upgraded version, however needless to say, I'm not using every single feature in AR.

Note: Someone should probably rip out the references to NHibernate.ByteCode.Castle in AR, as it is obsolete as of NHibernate 3.2.

[Daniel15]

Have you encountered any issues with this so far, or is it all working as expected?

[justintoth]

I ran into issues and then read that ar is no longer supported so stopped dev.

Sent from my iPhone

On Nov 14, 2012, at 6:28 PM, Daniel Lo Nigro [email protected] wrote:

Have you encountered any issues with this so far, or is it all working as expected?

—
Reply to this email directly or view it on GitHub.

[Daniel15]

Fair enough. Did you migrate your application to another library (like Fluent NHibernate or just "raw" NHibernate)?

[justintoth]

Personally I'm still using Active Record (I'm just not putting effort into
upgrading its source code.) I still love the clean/easy approach of AR and
I can always call sprocs from it if it doesn't do something that I need. If
you don't need new SQL Server 2008 features like the geography type then
you can get away with still using it, and that's coming from a developer
who is always staying on the bleeding edge of technology. However, I
believe the "correct" answer these days would be to use Fluent NHibernate.

On Wed, Nov 14, 2012 at 11:44 PM, Daniel Lo Nigro
[email protected]:

Fair enough. Did you migrate your application to another library (like
Fluent NHibernate or just "raw" NHibernate)?

—
Reply to this email directly or view it on GitHubhttps://pull/2#issuecomment-10397404.