You end up with the view and underlying tables being named the same, which gives you the following error:
Msg 3705, Level 16, State 1, Line 4
Cannot use DROP VIEW with 'dbo.underlying_table' because 'dbo.underlying_table' is a table. Use DROP TABLE.
Prefacing the view name with 'v_' or something like that would fix the problem.
The generator is built to generate views with the same name as tables but in another schema (that must exists)