marthijn. » Visual Studio

Possible solution for NHibernate many-to-many criteria

Marthijn — Fri, 07 Jan 2011 10:44:12 +0000

In one of my .NET projects I’m using the NHibernate library for object-relational mapping. I’m mainly using the ICriteria interface to fetch data from the database. Unfortunately I ran into a function that got really complicated; how to query a many-to-many relationship. For example, I have a table containing posts and a table containing tags. The post datamodel contains a set with tags so in my mapping it’s a many-to-many relationship. I want my query to return all posts tagged with one or more specific tags. On this forum I found a solution. I’m not sure if this is the perfect solution, so feel free to suggest a better one.

public IList<Post> GetPostsByTags(IList<Tag> tags)
{
 ICriteria posts = this.Session.CreateCriteria<Post>();
 foreach (Tag t in tags)
 {
  posts.Add(Subqueries.Exists(DetachedCriteria.For<Post>("p2")
   .SetProjection(Projections.Id())
   .CreateAlias("p2.Tags", "t")
   .Add(Restrictions.Eq("t.Id", t.Id))
   .Add(Restrictions.EqProperty("p2.Id", "this.Id"))));
 }
 posts.SetResultTransformer(NHibernate.Transform.Transformers.DistinctRootEntity);
 return posts.List<Post>();
}

Using log4net to show NHibernate SQL in Visual Studio

Marthijn — Thu, 02 Dec 2010 10:15:28 +0000

I’m currently developing a web application in ASP.NET MVC and NHibernate. Since the application was very slow at some points I wanted to know which SQL queries NHibernate was executing. Since the log4net library was already included in the application I searched for a solution to output the SQL queries to the console in Visual Studio 2010 using log4net. I found the solution on this wiki and this blog post.

First thing you need to do is add a log4net section in your web.config if you don’t have one yet.

>
 ...
  name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler,log4net"/>
 ...
>

Then add the log4net section, and configure an appender and logger.

>
  name="DebugSQL" type="log4net.Appender.TraceAppender">
  type="log4net.Layout.PatternLayout">
  value="%date [%thread] %-5level %logger [%property{NDC}] - %message%newline" />
 >
 >
 
  name="NHibernate.SQL" additivity="false">
  value="DEBUG"/>
  ref="DebugSQL" />
 >
>

That’s all. Don’t forget to configure log4net in the Global.asax.

protected void Application_Start()
{
 log4net.Config.XmlConfigurator.Configure();
 ...
}

Using NUnit in Visual Studio 2010

Marthijn — Wed, 09 Jun 2010 12:13:10 +0000

Like in older versions of Visual Studio it is possible to use NUnit as an external tool in the new 2010 version. By creating a toolbar as well it is very easy to run your test suite. The usual way to add an external command is by clicking the menu Tools -> External Tools. However, by default this menu item is not visible. To enable this menu item go to Tools -> Settings -> Expert Settings.

The first step is download and install the latest version of NUnit since older versions are not compatible with .NET 4. NUnit version 2.5.5 can be downloaded here.

Now go to Tools -> External Tools:

I think this screen shot explains itself very well. Now its possible to add this external command to a tool bar. To do so go to View -> Toolbars -> Customize:

Press the New button and enter a name. Now open the Commands tab and add the external command (usually External Command 1 when you don’t have any other external commands) to the toolbar:

When clicking the NUnit button in the new toolbar the NUnit GUI starts and loads your test suite.