This is an unresolved issue in ASP.NET which was first reported in 2019:
There is a workaround which allows '___' (triple underscore) to be used instead of '.' (link)