-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client Generator #516
Comments
update: it seems you are using the t4 text template generator? I se nothing strange with the small code snippet. I have not looked that much on the generated code from t4, but I assume it will generate redundant namespaces just because it wad easier to implement it that way. If there are any methods or similar that need to be made public to make extending the code generation easier I am very open to do so. I had planned to make naming etc public, but never did. If the feature works good then I am open consider adding it to openriaservices (with a project setting for specifying namespace translations) |
Forgot to ask: |
Thanks for your reply, I think it's better to have settings for the client namespace |
Hey @Daniel-Svensson .Sorry, I found this is a misunderstanding of the Blazor web app (.net 8) structure. In the new structure, the client and server work together and the server side is not only the host of the client (I can say both server and client are new clients, one client on the browser and the other on the server). so we have to setup a new API server for Host OpenRiaServices. so we don't need to change anything |
Describe the bug
When I Implement a new code generator for the client based on
CSharpClientCodeGenerator
, the proxy class will change and increase the lines of code. for example, every proxy class moves to its namespace instead of all proxy classes inside a namespace.Before
After
I want to change the client proxy namespace through
in the Blazer web app (blazer 8), the server has access to the client *.dll and the server model caused conflict with the client model we should change the namespace of the client
The text was updated successfully, but these errors were encountered: