+1  A: 

As I mentioned in the comments it sounds like the issue is with NHibernate throwing up during the code generation. If you really want to use the attributes I would suggest getting the NHibernate source code and trying to attach the VS debugger to the VS instance that is doing the code generation, might help you figure out why it is failing.

Probably a better approach would be to follow this post by Brada on using NHibernate with RIA Services or watching this screencast on NHibernate with RIA Services. Both of those places seem to have working examples of them working together, so maybe start there instead of going down the route you're going.

Bryant
It doesn't seem possible to attach the VS debugger to the VS instance that is doing the code generation. I know the posts you mentioned and in both posts they apply a different (better) way of mapping, but before switching to Fluent NHibernate (which takes a lot of time in my situation) I want to make sure it's not possible at all.
PB
A: 

You can add preprocessor directives to your entities so that when compiled for silverlight the attributes are missing.

#if SILVERLIGHT
//nothing
#else
[class]
#endif
public class entity{
}
Aaron Fischer
Sounds like a good solution, but unfortunately this doesn't work either because it still tries to use the attributes.
PB
A: 

We had the same issue. Solution: Get rid of the attributes and just use XML for mapping.

Bytemaster
That is indeed a solution, I prefer to use FuentNHibernate with automapping
PB