search

microsoft / Omex

Shared components used by the Omex team to build scalable and highly available distributed systems
MIT License
71 stars 40 forks source link

Namespace conflict with autogenerated code. #101

Closed knstntn closed 1 year ago

knstntn commented 5 years ago

Context

I made new namespace Microsoft.Omex.Metrics.ApiClient and used this namespace for ApiClient generated using nswag https://github.com/RicoSuter/NSwag

Result is shown on this picture image

Current Behavior

Compilation failed because System resolved to Microsoft.Omex.System

Expected Behavior

Compilation is fine.

Possible Solution

I think proper solution would be to update nswag to generate code using global:: alias for System, and I plan to send report to them

But you cannot change all generators in the world, so I think it is appropriate to rename Microsoft.Omex.System to avoid namespace conflicts.

Environment

NSwag version 11.20.1

knstntn commented 5 years ago

Added PR for NSwag https://github.com/RicoSuter/NSwag/pull/2356

AndreyTretyak commented 1 year ago

Omex.System deprecated and we are not using Omex.System namespace anymore, thank you for pointing this out.