Not descriptive error when configuration fails

Jun 10, 2010 at 12:23 PM
Hi! I recently upgraded from Unity 1.2 to 2.0. I'm configuring my container using configuration file. Of course I made all necessery changes it it to comply with schema of version 2.0. I noticed that when configuration is not correct (a type defined does not exist) I'm getting error "The given assembly name or codebase was invalid". I think that with previous error I was getting a more reasonable error. Is there anything I can do?
Jun 10, 2010 at 6:55 PM

We are aware of the issues, unfortunately to get must of the rest of the goodness we got with the rewritten config, we had to sacrifice on the error messages. We'll hopefully be able to improve this in future versions.