Jimmy Bogard Blog - Latest Comments

Re: Persisting enumeration classes with NHibernate

jbogard — Wed, 09 May 2012 08:43:36 -0000

Yep - but the easiest way is to have all of the values in the DB, and just model it such that some are "built in" and can't be deleted/modified through your app, and some are custom. We usually use a "System" or "BuiltIn" bit flag to indicate this on that table.

Re: Language feature parity and the polyglot programmer

Dony — Tue, 08 May 2012 06:37:01 -0000

You can use most fluent interfaces from VB.NET, but -man- they really do look ugly compared to their C# counterparts. Especialy the use of lambda expressions for nearly anything creates an interface that's accessable from VB.NET, but nothing more. Supporting another interface with lots of optional (named) parameters is much more VB.NET minded, but you won't find it on any major project because C# cannot handle this interface so easily.

Yes, you can use nearly every C# library from VB.NET, but that doesn't mean it's suited for VB.NET. And you can't switch an entire company from VB.NET to C# just because of those o-so-beautiful fluent interfaces ...

Re: Strengthening your domain: The double dispatch pattern

matt kocaj — Tue, 08 May 2012 03:21:14 -0000

Since we're trying not to inject things into our model objects and we certainly don't want them concerned with knowing what a Repository is, then is a service (domain service) the appropriate place to have a Repository injected for acquiring items from other aggregates if that's the sort of logic that is required in some method of a domain object?

Re: Persisting enumeration classes with NHibernate

Carlos Alberto Costa Beppler — Mon, 07 May 2012 20:27:11 -0000

Hello, I have to map soma classes that are almost the same of this.

The difference is that in my case I have some prefedined values, but the user can add more values to the database (the enumeration is an entity).

There are any way to do this using NH?

Re: Persisting enumeration classes with NHibernate

jbogard — Mon, 07 May 2012 09:03:41 -0000

Copy-Paste from other projects, really. It wasn't an intentional decision one way or the other, other than it seemed that PrimitiveType had less to implement out of the box than IUserType.

Re: Persisting enumeration classes with NHibernate

cbp — Mon, 07 May 2012 05:20:27 -0000

Just a question - why did you use PrimitiveType instead of IUserType?

Re: Strategies and discriminators in NHibernate

matt kocaj — Sun, 06 May 2012 23:31:14 -0000

Hey Jimmy,

I can't get this method working for me. The line <subclass discriminator-value="1" extends="PricingStrategy" name="PricingStrategy+FullPriceStrategy"> is giving me trouble.

I get the exception: NHibernate.MappingException: persistent class
PricingStrategy+FullPriceStrategy not found.

Any ideas?</subclass>

Re: Persisting enumeration classes with NHibernate

Никита Говоров — Sun, 06 May 2012 01:35:33 -0000

Probably better to use 'typedef' to reduce count of full qualified type name strings:
<typedef class="Namespace.To.EnumerationType`1[[Color, AssemblyWithDomainEnum]], AssemblyWithNHibCustomType" name="ColorEnum">

...

Re: Limits of performance optimization

Nick — Fri, 04 May 2012 16:12:19 -0000

haha yep. That's what I was saying Jason. A bit of awareness of the hole you're digging for yourself.

Re: Organizing ASP.NET MVC solutions

man — Fri, 04 May 2012 08:24:34 -0000

这不是一个问题

Re: Limits of performance optimization

Jason Meckley — Fri, 04 May 2012 08:16:22 -0000

Jimmy's not suggesting there should be 10 layers of abstraction. The point is to balance performance with maintainability. To far in either direction creates a problem.

Re: TestDriven.NET keyboard shortcut

Mert — Fri, 04 May 2012 04:35:04 -0000

That is what I was looking for. You need to set the “Use new shortcut in:” to “Text Editor”. Otherwise current TextEditor shortcut will override your global choice, and it won't work.

Re: Limits of performance optimization

Nick — Thu, 03 May 2012 10:51:09 -0000

Sometimes you can make beautiful code that is easy to maintain and looks great. But your data-access and network are abstracted 10 layers deep.

Try and optimise that son. Or even better - diagnose it.

A bit of awareness of what is all I'm saying based on experience of facades, wrapping, controllers, wrapping god knows what with 50 database and web service calls scattered from top to bottom of the stack.

Re: Limits of performance optimization

Gene Hughson — Thu, 03 May 2012 09:52:12 -0000

Bravo. Doggedly eking out every ounce of a given QOS criteria (performance, security, etc.) without thought to cost and need is as detrimental as sloppy work.

Re: Custom errors and error detail policy in ASP.NET Web API

jbogard — Thu, 03 May 2012 08:47:21 -0000

Ha, that's much easier than my way, which was unlocking each status code at a time. Thanks!

Re: Persisting enumeration classes with NHibernate

jbogard — Thu, 03 May 2012 08:45:34 -0000

Ugly, no?

Why no Fluent NHibernate? It's really easy to migrate/have both in one project.</property>

Re: How we do MVC – View models

Rlcristobal — Thu, 03 May 2012 08:08:24 -0000

Great job Jimmy! Ilove automapper

Re: Custom errors and error detail policy in ASP.NET Web API

Jan Ove S. Olsen — Thu, 03 May 2012 04:36:14 -0000

Also, when hosting ASP.NET WebAPI in IIS, add the following to web.config to makes IIS not eat the body of your custom error responses.

<configuration>
<system.webserver>
<httperrors existingresponse="PassThrough">
</httperrors></system.webserver>
</configuration>

If you're running IIS7/7.5 on a "security hardened" server, you'll need to run the following commands to "unlock" that config section:

cd C:\Windows\System32\inetsrv

appcmd unlock config /section:httpErrors

See details here: http://stackoverflow.com/quest...

Regards,
Jan Ove

Re: Persisting enumeration classes with NHibernate

matt kocaj — Thu, 03 May 2012 04:12:31 -0000

And this does or does not create a lookup table for the
TEnumeration items? Or is it the same as my SO example (http://stackoverflow.com/a/104..., where it simply tells NHibernate how to link the index/value field?

Re: Persisting enumeration classes with NHibernate

matt kocaj — Thu, 03 May 2012 03:24:30 -0000

And the HBM mapping example? (as much as I'd love the freedom to be using Fluent on this project)

Re: Seamless test authoring with ReSharper and AutoHotKey

Jimmy Bogard — Wed, 02 May 2012 20:00:07 -0000

Awesome, thanks!

Re: Seamless test authoring with ReSharper and AutoHotKey

Joseph Leo — Wed, 02 May 2012 18:42:14 -0000

I'm coming across this nearly 3 years after it was written and still finding tremendous value in it. Thanks for your post!

Re: The case for two-way mapping in AutoMapper

Ted Driggs — Wed, 02 May 2012 14:57:57 -0000

On further examination, I think you're right not to support it - there shouldn't be enough places where the EditModel to Entity conversion is taking place to make the mapping worthwhile.

For now I've refactored that conversion process out into a method in the entity's controller which also validates the EditModel. Not sure if this is a great idea, but I need to do validation that can't be expressed in data annotations and this ensures only valid EditModels ever even become entities.

Re: Custom errors and error detail policy in ASP.NET Web API

Jalpesh Vadgama — Wed, 02 May 2012 11:58:35 -0000

Nice work!! Would love to see more post from you on asp.net mvc 4.0

Re: Persisting enumeration classes with NHibernate

Sandor Drieënhuizen — Wed, 02 May 2012 08:44:46 -0000

I like to use the following simple solution to having enums mapped as integers, using only a small FluentNHibernate mapping convention:

    public class EnumConvention : IUserTypeConvention
    {
        public void Accept(IAcceptanceCriteria<ipropertyinspector> criteria)
        {
            criteria.Expect(n => n.Property.PropertyType.IsEnum);
        }

        public void Apply(IPropertyInstance instance)
        {
            // Map using the integral representation of the enum value.
            instance.CustomType(instance.Property.PropertyType);
        }
    }

Further, it's important to assign explicit integral values to our enum, to ensure that the integral representation of the enum values stays the same when a new value is added for example:

enum MyEnum
{
FirstValue = 1,
SecondValue = 2
}

Ofcourse, this is no more safe than enums are in C# but it suits me well.</ipropertyinspector>