So based on my experiments so far with prod mode on v16
Publishing production, views still in the ‘views’ folder
I think that uSync (current and soon to be updated version) are doing the right thing in terms of template production.
If you are compiling your views into the dll, then you can choose to exclude views from being published with your content , in the .csproj
<ItemGroup>
<Content Update="Views/**">
<CopyToPublishDirectory>Never</CopyToPublishDirectory>
</Content>
</ItemGroup>
and the views folder will be empty when you publish.
if you have a uSync folder with it’s template folder then that is expected. and when you import via uSync it will create the Templates via Umbraco which does the DB stuff, and no files are created on disk
I think in v16 - Umbraco is not creating the files, so while uSync has a load of code to detect and delete them when in production that code is never hit because the files are not there.
The view in the Umbraco backoffice is confusing and I think broken, in that it shows you these ‘empty’ templates when you look and if you try and save anything you get an error,
but
the templates are there in the code ,and linked to the content correctly (via the db stuff). and the front end should work fine.