NHibernate.XmlSerializers

[dhtroy]

We have a single developer that has started receiving the following
error message, when the call is issued to Configuration.AddAssembly(),
to add our mapping assembly. He has built the mapping assembly and
verified that it exists, physically, on his machine, and has performed
a clean and full solution rebuild, yet he continues to get this
error.

He disabled MDA's and this exception is no longer being thrown.

Can someone suggest a reason this is happening?

Exception Message:

The assembly with display name 'NHibernate.XmlSerializers' failed to
load in the 'LoadFrom' binding context of the AppDomain with ID 1. The
cause of the failure was: System.IO.FileNotFoundException: Could not
load file or assembly 'NHibernate.XmlSerializers, Version=2.0.1.4000,
Culture=neutral, PublicKeyToken=aa95f207798dfdb4' or one of its
dependencies. The system cannot find the file specified.

File name: 'NHibernate.XmlSerializers, Version=2.0.1.4000,
Culture=neutral, PublicKeyToken=aa95f207798dfdb4'

[Ayende Rahien]

Just ignore this issue, it will be caught internally inside the xml serializer infrastructure

[dhtroy]

Ayende,

Thanks for the fast response. Is there something he can do (i.e.,
disable) to prevent this from showing up (other than kill off all the
MDAs)?

Is there one particular MDA he can disabled so this no longer
displays?

Thanks again.

[Dario Quintana]

when you enable the option to see all CLR exceptions, you will be notified of every exception thrown, whether be caught or not.
Disable the option if you don't want to see the exceptions, or check just the excepcions you may want to see.

In VS: "Debug" -> "Exceptions" -> "Common Language Runtime Exceptions" -> See the "Thrown" check

--
Dario Quintana
http://darioquintana.com.ar