Just curious: Why is this very convenient and commonly used Timer class placed in the "System.ComponentModel.TypeConverter" assembly?

[Flithor]

https://github.com/dotnet/runtime/blob/main/src/libraries/System.ComponentModel.TypeConverter/src/System/Timers/Timer.cs

Is the simple answer "historical legacy"?

[huoyaoyuan]

Is the simple answer "historical legacy"?

Yes, and more. There are several different implementations of timer in .NET:

and System.Threading.Timer is the most low-level one. The new TimeProvider is also integrated with System.Threading.ITimer. As you can see in the implementation, System.Timers.Timer is also a wrapper on top of System.Threading.Timer.

[Flithor]

Because this assembly is for TypeConverters, so looks confusing that putting a type that obviously doesn't match the assembly name.
"historical legacy" also means that it is cannot to move it, and the type put into a wrong assembly issues are far less important than compatibility issues.

[huoyaoyuan]

It can be moved without breaking compatibility, just some extra effort is required.

I didn't find a particular reason for the assembly of this type. It's quite orphaned with no dependents found. System.ComponentModel.Primitives has all required dependencies, but doesn't feel "suitable". The answer may be simply "there's no best location" at all.

[Flithor]

Maybe the author of this class: "I don't know where should I to put this, so I just put it here."