When converting the sample code for Custom Numbering that comes along with the SDK from C# to VB, one of our users reported that he was now facing the error 4112, i.e. NumberingSchemeProviderCouldNotBeLoaded.
Solution:
In case of VB, it seems that there is a Root Namespace that is added before every Namespace, which should also be included in the 'type' attribute in web.config. If you add that, it should be able to initialize correctly. So the following should get it to work:
<numberproviders>
<numberprovider name="CustomProvider" type="CustomNumberingProvider.CustomNumberingProvider.CustomNumberingProvider, CustomNumberingProvider" cancache="false">
<!-- <initializationParm value="somethingImportant" /> -–>
</numberprovider>
</numberproviders>
