In process of switching my big old enterprice system from sync model to sync+async model with this ISG, I noticed that the ISG can produce a very long cs name if cs's namespace is long itself.
I did not face with problems but I suspect the problems can arise if g.cs filename + emit compiler generated folder will be longer than 260 symbols.
To see the potential issue put the following inside of csproj witch consumes ISG:
In process of switching my big old enterprice system from
sync
model tosync+async
model with this ISG, I noticed that the ISG can produce a very long cs name if cs's namespace is long itself.I did not face with problems but I suspect the problems can arise if
g.cs
filename + emit compiler generated folder will be longer than 260 symbols.To see the potential issue put the following inside of csproj witch consumes ISG:
May be the better behaviour is to truncate the name of
g.cs
file if it is too long.just fyi, I may be wrong.