Library name

System.ClientModel

Please describe the feature.

Given that we have an assembly wide ModelReaderWriterContext if a single model that needs a builder has the Experimental attribute then the entire context class needs it which makes all model reading / writing appear to be experimental when its not.

Option 1

Move to 1 context per model

Option 2

Split into 2 context one hosting the experimental builders one hosting everything else. The experimental context would forward to the non experimental context allowing for back compat if/when a model moves from experimental to non.