You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.
When using previous versions of the framework, one could customize the behavior of the designer generated classes by choosing ResXFileCodeGenerator or PublicResXFileCodeGenerator as the Custom Tool in order to get the classes and properties internal or public.
Now, it seems that there is no way to choose, and the generated classes and properties are internal.
There are many side-effects if the default internal behavior can not be changed:
It does not only apply to MVC Models. It also prevents using DataAnnotations for other validation frameworks, such the one used at EntityFramework or FluentValidation.
It also makes not possible to have a shared resources file with solution wide translations used in several projects.
If it's difficult to change the project.json or .xproj syntax to allow the behavior selection, IMO the default behavior of the generator should be public, since it allows all the scenarios.
The text was updated successfully, but these errors were encountered:
When using previous versions of the framework, one could customize the behavior of the designer generated classes by choosing ResXFileCodeGenerator or PublicResXFileCodeGenerator as the Custom Tool in order to get the classes and properties internal or public.
Now, it seems that there is no way to choose, and the generated classes and properties are internal.
There are many side-effects if the default internal behavior can not be changed:
DisplayAttribute does not work: aspnet/Localization#134
It does not only apply to MVC Models. It also prevents using DataAnnotations for other validation frameworks, such the one used at EntityFramework or FluentValidation.
It also makes not possible to have a shared resources file with solution wide translations used in several projects.
If it's difficult to change the project.json or .xproj syntax to allow the behavior selection, IMO the default behavior of the generator should be public, since it allows all the scenarios.
The text was updated successfully, but these errors were encountered: