If there is a need to update ReLinq, it's only a matter of taking the
NH the source, putting the new relinq library in the lib folder,
running ShowBuildMenu.bat and selecting F. You can then grab the new
dll from the build folder. As you say, beginners are better off with
the merged assembly anyways.
Note that we don't just merge everything to make it easy to use. We
merge libraries that are theoretically only used internally. If the
public interface to NHibernate is not sufficient, we will correct
those deficiencies.
Merging with internalization also allows users to utilize different
versions of libraries with no problems. For example, Antlr is a
popular library, but NHibernate is tied to a particular version. If
you want to use Antlr in your own project without merging, you'd need
to use the same version as NHibernate, which could cause problems.
Merging also isolates users from changes to these internal libraries,
such as the recent name change of the Remotion.Linq assembly.
Patrick Earl
On Fri, Apr 8, 2011 at 12:00 PM, Ramon Smits <[email protected]> wrote:
>
>
> I hope that we will have builds without ILMerged used for a release as minor
> updates to dependancies cannot be used because it is merged. NServiceBus
> made, IMHO, a bad decision by using the ILMerge version as default release.
> Please don't make that same mistake! I agree that having a ILMerged version
> is much easier for beginners but its not that you decide to change all
> dependancies all the time.
>
> --
> Ramon
>
