I too have no time to mess with Ruby, so I just pull up the sln file
in Visual Studio 2008 and build it myself.

While I'm in there, since I copy the latest NHibernate 2.1.0 Beta 2
build DLL's over to Fluent NHibernate's tools\NHibernate\ directory
and make the following changes to my copy of the code, located in C:
\Fluent NHibernate\ :

Add the following lines to the bottom of MsSqlConfiguration.cs located
in C:\Fluent NHibernate\src\FluentNHibernate\Cfg\Db\:

         public static MsSqlConfiguration MsSql2008
         {
             get { return new MsSqlConfiguration
().Dialect<MsSql2008Dialect>(); }
         }

Change SessionSource.cs located in C:\Fluent NHibernate\src
\FluentNHibernate\to read as follows:

        public void BuildSchema(ISession session, bool script)
        {
            //new SchemaExport(configuration)
            //    .Execute(script, true, false, true,
session.Connection, null);
            new SchemaExport(configuration)
                .Execute(script, true, false, session.Connection,
null);
        }

Change all this:

OracleDataClientConfiguration().Dialect<Oracle9Dialect>()

To this:

OracleDataClientConfiguration().Dialect<Oracle9iDialect>()

Since Fluent NHibernate uses an older edition of NHibernate, I add the
following to app.config of Examples.FirstProject to get things to run
with the latest NHibernate 2.1.0.2002 (NHibernate 2.1.0 Beta 2):

  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

      <!--<publisherPolicy apply="no"/>-->

      <dependentAssembly>
        <assemblyIdentity name="nunit.framework"
publicKeyToken="96d09a1eb7f44a77" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535"
newVersion="2.4.8.0"/>
      </dependentAssembly>

      <dependentAssembly>
        <assemblyIdentity name="Castle.Core"
publicKeyToken="407DD0808D44FBDC" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-1.1.0.0"
newVersion="1.1.0.0"/>
      </dependentAssembly>

      <dependentAssembly>
        <assemblyIdentity name="Iesi.Collections"
publicKeyToken="AA95F207798DFDB4" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535"
newVersion="1.0.1.0"/>
      </dependentAssembly>

      <dependentAssembly>
        <assemblyIdentity name="NHibernate"
publicKeyToken="aa95f207798dfdb4" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-4.4.4.4444"
newVersion="2.1.0.2002"/>
      </dependentAssembly>

      <dependentAssembly>
        <assemblyIdentity name="Castle.DynamicProxy2"
publicKeyToken="407dd0808d44fbdc" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-4.4.4.4444"
newVersion="2.1.0.0"/>
      </dependentAssembly>

      <dependentAssembly>
        <assemblyIdentity name="NHibernate.ByteCode.Castle"
publicKeyToken="aa95f207798dfdb4" culture="neutral"/>
        <bindingRedirect oldVersion="0.0.0.0-4.4.4.4444"
newVersion="2.1.0.2002"/>
      </dependentAssembly>

    </assemblyBinding>
  </runtime>

It's a lot of extra work, but the point is, by using Visual Studio
2008 SP1, I can control which NHibernate is used and I can verify
easily by running Examples.FirstProject.

I am content to let the leaders of this project use whatever build
tools they like, so long as I have the option to use Visual Studio as
an alternative.

On Jun 8, 5:27 pm, fquednau <[email protected]> wrote:
> I have spent, sorry, wasted, the past hour to get some ruby running on
> this windows 7 machine. I have reached the point where some obscure
> part in ActiveRecord (Why would I need this for building
> FluentNhibernate?) screams for some ftools that apparently are part of
> any standard ruby library but not in mine. Hm.
>
> Maybe I am just too stupid but why on Earth do I have to install a
> script language with x gems and at the end I have to resort to open
> the solution file and compile the stuff?
>
> I know ruby is fashionable and all and you all have grown a huge
> allergy towards anything <that><looks><like><that> (There, now I've
> hit you!). But really, is it THAT much better than a silly little
> msbuild script or something like that?
>
> Will we have to target the DLR with a new script language, BUILDOR,
> with totally <> free syntax (yes, even i <= 2 will be i lt= 2) to make
> you guys happy?
>
> Right, enough ranting for now, I actually want to have some fun with
> FluentNhibernate!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Fluent NHibernate" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/fluent-nhibernate?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to