NHibernate 3.x changes

Working on a sample project for a perspective company - when enabled NuGet for FluentNHibernate, and saw a breaking change in the NhQueryable constructor. (I've been building from the source for awhile so this one passed me by, 2.x - 3.x introduced some breaking changes)

This breaks:
...
public ReadOnlyRepository(ISession session)
        {
            this.selection = new NhQueryable(session);
        }
....

This 'seemed' to work - at least the compiler didn't complain:
...

public ReadOnlyRepository(ISession session)
        {
            this.selection = new NhQueryable(session as ISessionImplementor);
        }
...

After a few unit-tests later I discover that the session passed in is NOT being preserved. Now what?

So I look at the IQueryOver interface - inside of Hibernate seems to add some Extension methods and a Linq-like interface; but I miss the more "natural" feel of regular Linq expressions. Granted, I won't have as much fine-control over the underlying query - but I'm not doing anything too crazy - yet.

I end-up changing the original interface/implementation from:
 public interface IReadOnlyRepository where TEntity : class  
  {  
      IQueryable Linq();  
  }  
...
#region IReadOnlyRepository Members

         public IQueryable Linq()
  {
   return this.selection.AsQueryable();
  }

#endregion
...

to the 3.x friendly:

public interface IReadOnlyRepository : IQueryable where TEntity : class
    {
        IQueryable AsQueryable(); 
    }
...

Note: The implementation then explicitly marshals the "queryable-ness" to my preserved session.

Also Note: the explicit usage of namespace System.Linq - otherwise it WILL conflict with Hibernate:

#region IReadOnlyRepository Members

        public System.Linq.IQueryProvider Provider
        {
            get { return session.Query().Provider; }
        }

        public System.Collections.Generic.IEnumerator GetEnumerator()
        {
            return session.Query().GetEnumerator();
        }

        System.Collections.IEnumerator System.Collections.IEnumerable.GetEnumerator()
        {
            return this.GetEnumerator();
        }

        public System.Type ElementType
        {
            get { return session.Query().ElementType; }
        }

       public System.Linq.Expressions.Expression Expression
        {
            get { return session.Query().Expression; }
        }

        public IQueryable AsQueryable()
        {
            return session.Query();
        }
        #endregion

Turns out this tripped out quite a few, as I searched the web. Hope this helps someone transitioning from building from source to moving to NuGet.

Why did I ever switch to MSTEST?

Ran into a wicked problem with MSTEST today, resurrected an old project went to run the tests - and boom - nothing appeared to run - very similar to the "cylon" symptom I talked about in 2010. Eventually ran into this wonderment which gave me at least an indication of what was happening (and only 2 days after latest VS2012 update too...hmmm)

So I waded through the following links to try and discover what was happening...

Came across a number of Open, Closed and Unreproducable issues from Microsoft Connect. Then finally a Resharper related post seemed like it was worth trying out (super shoutout to JetBrains forums). 

So I ended up switching from MSTEST to NUNIT and all tests ran. (Big Surprise)
I am reminded of an old song going back to NUNIT...

So how to switch in between NUNIT/MSTEST quickly - use a build directive - NUNIT.
Add the following code to the the head of your test files (or possibly a partial class, or just a plain base-class that all test files inherit from). Then you are basically remapping the MSTEST attributes to the appropriate NUNIT ones. You are rocking with NUNIT - thank you Resharper & StackOverflow. 
(Note: There is no TestContext available in NUNIT so if you rely heavily on that you will have to do something else)


#if NUNIT
using TestClass = NUnit.Framework.TestFixtureAttribute;
using TestMethod = NUnit.Framework.TestAttribute;
using TestCleanup = NUnit.Framework.TearDownAttribute;
using TestInitialize = NUnit.Framework.SetUpAttribute;
using ClassCleanup = NUnit.Framework.TestFixtureTearDownAttribute;
using ClassInitialize = NUnit.Framework.TestFixtureSetUpAttribute;
#else
using Microsoft.VisualStudio.TestTools.UnitTesting;
#endif

StackOverflow

http://osherove.com/blog/2010/3/5/nunit-vs-mstest-nunit-wins-for-unit-testing.html

OpenStack

Entice Me
Opening my eyes and looking around to see what is available. Willing to relocate for the right opportunity or area (I like the coast). I bring a great deal to the table and I'm kinda fun to work with...let's see what we can do for each other.

Curriculum Vitae/Resume
Zerply-Profile 

Ninject + MVC 4

Nothing earth shattering here - but was wrestling with current WCF services and trying to leverage the delicious newness of the WebApi with Ninject 3.0. A bit of pain and a few tears later...

   1:  public class MvcApplication : NinjectHttpApplication

   2:      {

   3:          /// <summary>

   4:          /// Called when [application started].

   5:          /// </summary>

   6:          protected override void OnApplicationStarted()

   7:          {

   8:              base.OnApplicationStarted();

   9:   

  10:              AreaRegistration.RegisterAllAreas();

  11:              FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters);

  12:              RouteConfig.RegisterRoutes(RouteTable.Routes);

  13:              BundleConfig.RegisterBundles(BundleTable.Bundles);

  14:          }

  15:   

  16:          /// <summary>

  17:          /// Creates the kernel.

  18:          /// </summary>

  19:          /// <returns>IoC container object</returns>

  20:          protected override IKernel CreateKernel()

  21:          {

  22:              IKernel kernel = new StandardKernel(new NinjectSettings { LoadExtensions = true });

  23:   

  24:              // add AutoMapper to the core -> needs to be first; as services will use this.

  25:              kernel.Bind<ITypeMapFactory>().To<TypeMapFactory>();

  26:              kernel.Bind<ConfigurationStore>().ToConstant(new ConfigurationStore(kernel.Get<ITypeMapFactory>(), MapperRegistry.AllMappers())).InSingletonScope();

  27:              kernel.Bind<IConfiguration>().ToMethod(c => c.Kernel.Get<ConfigurationStore>());

  28:              kernel.Bind<IConfigurationProvider>().ToMethod(c => c.Kernel.Get<ConfigurationStore>());

  29:              kernel.Bind<IMappingEngine>().To<MappingEngine>();

  30:   

  31:              kernel.Bind(

  32:                  x =>

  33:                  x.FromAssembliesMatching(new[]

  34:                      {

  35:                          "*.Service.dll", "*.Service.Mvc.dll", "*.Service.Data.dll"

  36:                      }).SelectAllClasses().BindAllInterfaces());

  37:              kernel.Bind<ServiceHost>().To<NinjectServiceHost>();

  38:                          

  39:              // not intended to be used when deriving from NinjectHttpApplication <sigh>

  40:              ////kernel.Bind<IHttpModule>().To<HttpApplicationInitializationHttpModule>();

  41:              ServiceLocator.SetLocatorProvider(() => new NinjectServiceLocator(kernel));

  42:              var locator = new NinjectServiceLocator(kernel);

  43:              ServiceLocator.SetLocatorProvider(() => locator);

  44:              return kernel;

  45:          }

  46:      }

Well - its been awhile. I've been mostly tweeting and/or G+ Anyway, new look. New trends. Job Trends 2012

SheepAOP::SheepAspect

Another aspect orientated framework -SheepAOP now SheepAspect by Hendry Luk.

I'm glad to see someone else in this space. I'm also happy to see that it is derived with an IoC container in mind. Seems straightforward enough - could have some real promise. I will keep this framework in mind for any future projects.

http://sheepaspect.codeplex.com/

http://hendryluk.wordpress.com/2011/05/08/sheepaop-part-1-getting-started/