We now have enough knowledge of type provider, not just the concept of using a sample type provider and implementing a custom type provider but also that there might be pitfalls as well. In this section, the common pitfalls in type providers are wrapped as a simplified list with a simple explanation as well.
Common pitfalls in implementing type providers are quite subtle but these are important:
Type provider strategy has to be planned first. The planning must also include the infrastructure to ease the metadata generation, whether it employs erased or generative strategy. Do not always assume that we can always provide generative type providers instantly. Failing to provide type resolution with the namespace will yield undesirable results, including erased type metadata.
Reflection should use lazy implementation instead of an eager one. This lazy evaluation should not be combined with asynchronous reflection because cross-thread exception will...