Discussion:
[nhusers] NHibernate and 64-bit Support
Vikram Srivatsa
2017-06-07 08:55:02 UTC
Permalink
Currently an application that we are dealing with uses NHibernate v2.2 and
the Application itself is on .NET v4.6.2. The application is SOA based and
comprises of multiple WCF Services. We are not able to have the IIS AppPool
settings at 64-bit due to the v2.2 of NHibernate. Does upgrading NHibernate
v2.2 to the latest v4.1.1 enable us to eliminate the 32-bit dependency as
that is our primary objective in doing the upgrade.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nhusers+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
Oskar Berggren
2017-06-07 16:34:57 UTC
Permalink
I wasn't aware of any 64-bit problem in 2.2, but for sure I'm running NH
3.3 on 64-bit for many years with no problem.

A requirement is of course that the underlying ADO.Net database driver
doesn't use native 32-bit only code. Have you checked to make sure this
isn't the problem here?

/Oskar
Post by Vikram Srivatsa
Currently an application that we are dealing with uses NHibernate v2.2 and
the Application itself is on .NET v4.6.2. The application is SOA based and
comprises of multiple WCF Services. We are not able to have the IIS AppPool
settings at 64-bit due to the v2.2 of NHibernate. Does upgrading NHibernate
v2.2 to the latest v4.1.1 enable us to eliminate the 32-bit dependency as
that is our primary objective in doing the upgrade.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nhusers+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
Vikram Srivatsa
2017-06-08 12:52:29 UTC
Permalink
Thanks for your quick response - I will double check on that. Coming to
NHibernate v4.1.1 - I had a few more questions.

1. Is there a specific 64-bit version of NHibernate that I need to download
or does NHibernate binaries use "any cpu" and hence based on the host it
would work as either 32 - bit or 64 - bit
2. Any information on compatibility issues that one needs to be aware of in
attempting an upgrade from v2.2 to v4.1.1 would also be extremely helpful.
Post by Oskar Berggren
I wasn't aware of any 64-bit problem in 2.2, but for sure I'm running NH
3.3 on 64-bit for many years with no problem.
A requirement is of course that the underlying ADO.Net database driver
doesn't use native 32-bit only code. Have you checked to make sure this
isn't the problem here?
/Oskar
Post by Vikram Srivatsa
Currently an application that we are dealing with uses NHibernate v2.2
and the Application itself is on .NET v4.6.2. The application is SOA based
and comprises of multiple WCF Services. We are not able to have the IIS
AppPool settings at 64-bit due to the v2.2 of NHibernate. Does upgrading
NHibernate v2.2 to the latest v4.1.1 enable us to eliminate the 32-bit
dependency as that is our primary objective in doing the upgrade.
--
You received this message because you are subscribed to the Google Groups
"nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an
<javascript:>.
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nhusers+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
Oskar Berggren
2017-06-17 11:10:34 UTC
Permalink
NH is built for "Any CPU".

/Oskar
Post by Vikram Srivatsa
Thanks for your quick response - I will double check on that. Coming to
NHibernate v4.1.1 - I had a few more questions.
1. Is there a specific 64-bit version of NHibernate that I need to
download or does NHibernate binaries use "any cpu" and hence based on the
host it would work as either 32 - bit or 64 - bit
2. Any information on compatibility issues that one needs to be aware of
in attempting an upgrade from v2.2 to v4.1.1 would also be extremely
helpful.
Post by Oskar Berggren
I wasn't aware of any 64-bit problem in 2.2, but for sure I'm running NH
3.3 on 64-bit for many years with no problem.
A requirement is of course that the underlying ADO.Net database driver
doesn't use native 32-bit only code. Have you checked to make sure this
isn't the problem here?
/Oskar
Post by Vikram Srivatsa
Currently an application that we are dealing with uses NHibernate v2.2
and the Application itself is on .NET v4.6.2. The application is SOA based
and comprises of multiple WCF Services. We are not able to have the IIS
AppPool settings at 64-bit due to the v2.2 of NHibernate. Does upgrading
NHibernate v2.2 to the latest v4.1.1 enable us to eliminate the 32-bit
dependency as that is our primary objective in doing the upgrade.
--
You received this message because you are subscribed to the Google
Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nhusers+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
f***@free.fr
2017-06-28 10:50:04 UTC
Permalink
Check release
notes. https://github.com/nhibernate/nhibernate-core/blob/master/releasenotes.txt

Some common issues: no need to use an external proxy factory anymore,
System.Generic.Collection interfaces replacing Iesi ones (ISet) since v4.
Post by Vikram Srivatsa
Thanks for your quick response - I will double check on that. Coming to
NHibernate v4.1.1 - I had a few more questions.
1. Is there a specific 64-bit version of NHibernate that I need to
download or does NHibernate binaries use "any cpu" and hence based on the
host it would work as either 32 - bit or 64 - bit
2. Any information on compatibility issues that one needs to be aware of
in attempting an upgrade from v2.2 to v4.1.1 would also be extremely
helpful.
Post by Oskar Berggren
I wasn't aware of any 64-bit problem in 2.2, but for sure I'm running NH
3.3 on 64-bit for many years with no problem.
A requirement is of course that the underlying ADO.Net database driver
doesn't use native 32-bit only code. Have you checked to make sure this
isn't the problem here?
/Oskar
Post by Vikram Srivatsa
Currently an application that we are dealing with uses NHibernate v2.2
and the Application itself is on .NET v4.6.2. The application is SOA based
and comprises of multiple WCF Services. We are not able to have the IIS
AppPool settings at 64-bit due to the v2.2 of NHibernate. Does upgrading
NHibernate v2.2 to the latest v4.1.1 enable us to eliminate the 32-bit
dependency as that is our primary objective in doing the upgrade.
--
You received this message because you are subscribed to the Google
Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "nhusers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nhusers+***@googlegroups.com.
To post to this group, send email to ***@googlegroups.com.
Visit this group at https://groups.google.com/group/nhusers.
For more options, visit https://groups.google.com/d/optout.
Loading...