Regional Settings Impact Soap Client generation
See original GitHub issueI have an issue on the Wcf Client generator on Dotnet Core projects. When generating the code, if you have your computer regional settings set to something non english ( comma used in decimals or dots). the generated code will not compile.
If i put my regional settings to dutch, this is the output (will not compile):
this.initial_Costs_AmountField = ((decimal)(0,0m));
and if i put my regional settings to english (united states) this is the output (does compile):
this.initial_Costs_AmountField = ((decimal)(0.0m));
Is this a configuration thing or a bug?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Web Services Internationalization Usage Scenarios
A SOAP Processor implementation might provide accessible natural language or locale preference information, received either in the transport ( ...
Read more >Regional settings - Service Manager - ITOM Practitioner Portal
Regional settings define local values for month names and abbreviations, date format, system language, and default system currency.
Read more >Configuring Microsoft Dynamics NAV Server
Specifies the client type that is used to generate URLs when the client type is set to Default. The options are Current, Windows,...
Read more >Code Generation Tools for Web Services | SoapUI
Easy multi-environment switching. Detailed test history and test comparison reporting. ReadyAPI. Support for SOAP, REST, and GraphQL API Testing.
Read more >gSOAP user guide
Introduction. The gSOAP toolkit offers C/C++ tools and libraries to implement efficient and secure SOAP, XML, JSON and REST client and service Web...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is now fixed in dotnet-svcutil v1.0.4.
Great 👍 If there is anything else you need just let me know!