I have encountered a problem when using NHibernate 1.0.1 and NHibernate 1.0.2 that I did not have when I was using NHibernate 1.0.0 and earlier.

I am using Visual C# 2005 as my IDE. When I start my program, it loads the NHibernate.dll and Iesi.Collections.dll assemblies, but it also attempts to load assemblies with seemingly random names, like the following...

(Managed): Loaded 'NHibernate.dll', No symbols loaded.
(Managed): Loaded 'dvobrs-w', No symbols loaded.
(Managed): Loaded 'knxq7ihp', No symbols loaded.
(Managed): Loaded 'Iesi.Collections.dll', No symbols loaded.
(Managed): Loaded 'mjh2avkr', No symbols loaded.
... this continues on for over 50 lines

This problem only occurred after I upgraded to NHibernate 1.0.1. The problem did not go away after upgrading to NHibernate 1.0.2.

Does anyone know what I might be doing wrong?

Thanks.

I think I have seen something similar with ASP.NET. It it a Web application or WinForms? If it is a Web app, make sure you don't have copy local set to true for your NH DLLs. ASP.NET doesn't like strongly named DLLs in the BIN folder.

Thanks for the tip!

It is a Windows Forms application. If I don't put the NHibernate DLL in the same directory as my executable, does that mean I have to put it in the global assembly cache? I would prefer not to do so.

The assemblies that you see in the output window are generated by the reflection optimizer that is in NHibernate from 1.0.1. You can turn it off in the configuration if you want.

Thank you very much. Disabling the reflection optimizer has solved my problem.

I have been unable to understamd what is You problem? The fact that some auto-generated assemblies are loaded should not cause troubles, right?

I am not at all familiar with what the reflection optimizer does and how it works, but when I saw what appeared to be assemblies with random-looking names being loaded, I thought that it was probably an error of some sort. This, coupled with the fact that the load time for my program increased by a large amount, led me to consider this to be a problem.

I probably should have made that more clear in my initial post.

The increased load time might be considered as problem indeed.

You indicated that there are some 50 random-named asemblies loaded? Could anyone explain why there are so many of them?

I am also experiencing this 'problem'. when I load the configuration it takes about 10 to 15 seconds to load. While it is loading, the random-name assemblies are loaded.

I currently have about 40 mappings that are in the same library as my dao classes (XXXX.DAO.dll) and the business object classes are in a separate library (XXXX.Shared.dll).

When the optimizer is disabled, initialization takes about one second. Performance of queries and crud operations seem to be about the same (maybe a little slower, but not much).

If there is anything I can do to help with this, please let me know.