System.Reflection.AmbiguousMatchException: Ambiguous match found.

If you get this error with NetTiers, it’s probably because you have a field named with a reserved word such as: Tag ID SortOrder Rename the field

October 20, 2009 · 1 min

completely close and re-open NetTiers after database changes

If you have NetTiers open and have generated code, then make changes to the database, you need to completely close and re-open CodeSmith / NetTiers for it to fully recognise the changes. Something or other gets cached and NetTiers doesn’t spot the database changes – this was a pain to track down.

September 24, 2009 · 1 min

SortOrder

Don’t call a field in the database “SortOrder” It breaks nettiers in subtle ways that are hard to spot

September 23, 2009 · 1 min

empty fields

I’d set up the MedicineExaminers system to not allow nulls on any fields – they were supposed to contain empty strings if there was no data e.g. no email address. The NetTiers generated site didn’t like this as it made the fields required. I’ve changed the fields to allow nulls and so now, if I have an empty text box, NetTiers sets the value to null in the database. Lookup lists (e.g. speciality) will have values such as “not known”, so foreign keys will never need to be null.

April 3, 2008 · 1 min