Ambiguous reference in projects that have transitive dependencies on both MassTransit.Abstractions and NewId about newid HOT 5 CLOSED

This was intentional to prevent two separate packages using the same algorithm from generating the same identifiers. While I can understand the transitive package issue, a better option might be an empty NewId package – but I don't think that would work either.

from newid.

Yeah, sorry. I did not mean to be prescriptive about a solution. That was just the first one that came to mind.

from newid.

Right, I get it. Eliminating the old package from your dependency chain would be the best course of action.

from newid.

Fantastic ID generator you guys have made here! Sorry if I'm being ignorant here, but wouldn't it be much easier to just keep it in it's own separate namespace, like "NewId" or..?

from newid.

Fantastic ID generator you guys have made here! Sorry if I'm being ignorant here, but wouldn't it be much easier to just keep it in it's own separate namespace, like "NewId" or..?

Long story, but NewId was originally in MassTransit, later it was moved out to use it in other projects but the namespace remained the same to avoid breaking compatibility/builds. Now it's back in MassTransit.Abstractions (no namespace change required).

The problem with pushing a new v4 with the NewId namespace would be the duplication of the logic in the same process (people will screw up, they do it all the time and end up using both) resulting in duplicate Guids.

OH, and the whole static class with the same name as the namespace nonsense.

from newid.