Using full names of generated types to avoid ambiguities with existing namespaces #4970

Using full names of generated types to avoid ambiguities with existing namespaces

Usage Workflow file

10 errors

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)

The type or namespace name 'Client' does not exist in the namespace 'App.Client.App' (are you missing an assembly reference?)