Moving @bparks13 email comments to this discussion

Due to the accessibility of the type converters, I would have to make every single type converter public, as well as make the base class public, if I want to call the converter directly from the Design library

It isn’t a huge amount of code, so I could reimplement it, but that is something we are trying very hard not to do

Question: is it worth exposing all of the type converters in the public interface to make this an easy fix? Or do we just leave it

as-is for now, knowing that a user could potentially see these fields and modify them expecting it to do something when in reality it does nothing?

There is this page on SO showing it might be possible using reflection, if that is something we wanted to do without making the classes public

My opinions

• I don't think we want to make this public
• Reflection is probably the way to to go
• We can release 0.4.0 without this, so if you think its going to hold things up then lets move to 0.5.0

@aacuevas Suggests the following as alternative method without reflection or changing the public interface:

https://stackoverflow.com/questions/920844/how-can-i-access-an-internal-class-from-an-external-assembly
https://learn.microsoft.com/en-us/dotnet/standard/assembly/friend?redirectedfrom=MSDN