Re: [fluent-nhib] 2010 / .net 4 upgrade & FNH runtime crash?

2010-04-14 Thread Paul Batum
You should be able to find the details in the inner exception. Are you sure there are no other details? If you still can't see something, turn on "break on all CLR exceptions", that should help determine the underlying cause. On Wed, Apr 14, 2010 at 6:46 PM, Berryl Hesh wrote: > This is happenin

[fluent-nhib] Re: Automappings and table-per-class-hierarchy

2010-04-14 Thread Berryl Hesh
I find the same behavior too - I can't set the column name of the discriminator and I can't override the default behavior of using the fully qualified type as the discriminator value. I posted a question here a few weeks ago looking for a way to see if there was a convention I could use and how to

[fluent-nhib] 2010 / .net 4 upgrade & FNH runtime crash?

2010-04-14 Thread Berryl Hesh
This is happening only in runtime; I get an the basic "Database was not properly configured" error msg without any detail. Tests all run without a hitch. It's a WPF app. The "only" change was migrating to 2010 and changing the target to .net 4.0. Help appreciated!! Cheers, Berryl -- You receiv

[fluent-nhib] creating NONCLUSTERED INDEX on column by convention or fluent map

2010-04-14 Thread Rob#
Hi, I want to use schemaExport to generate my Database. So, I would like some help as one of my table needs to have a non-clustered index on one column. Is there any way I can use the IIndexConvention to implement it? I could use a custom attribute to distinguee the property and then apply the con

[fluent-nhib] Re: Automappings and table-per-class-hierarchy

2010-04-14 Thread Felipe Leusin
A follow-up: If u set the DiscriminatorColumn in the setup part of AutoMapper you can change the name of the column, ie: DiscriminatorColumn = type => (type == typeof(MyClass)) ? "IsHomeTeam" : "discriminator"; But I've been having no luck in determining a way to set DiscriminatorColumn type and