Not sure if I'm missing something here, as I don't usually generate EF Core 5... When the EntityClasses are generated some have an attribute [Browsable(false)] that doesn't resolve because the file has no 'using System.ComponentModel;' statement.

LLBLGen Pro v5.8 (RTM) Entity Framework Core v5

Reproduced.

Strange, build tests succeed here, but we'll look into it.

Well, I can't reproduce it, at least not with a project with entities and typed views. Could you tell me on which properties the attribute was present? I recreated a new project btw. If you migrated a project from another framework (e.g. Entity Framework 6 or LLBLGen Pro) to Entity Framework Core 5 by changing the target framework, the attributes defined on various elements by the original framework are still in the project. To fix that, go to the project settings -> Entity model -> Code generation -> Attributes and remove all the ones you don't need. [Browsable(false)] is something we only define in LLBLGen Pro RTF projects.

Yes, there is an Attribute Browsable($false) under the NavigatorSingleValue, possibly because this was originally using the LLBLGen framework. This thing of auto-added attributes has cropped up a few times for me. Given that they are set for generation automatically, perhaps the auto-created ones should either be removed when switching frameworks or a warning should be included in the output? Just a thought.

We actually thought about it, but it's unclear when the target framework is changed if they're autogenerated or manually added. As switching frameworks is rare we therefore didn't add code for it due to this ambiguity.