Limitations

The Object Browser is able to dynamically load .NET assemblies in order to deserialize objects and display their public properties and fields. The browser is well-suited for instantiating and displaying simple, self-contained object types that store data, but it is not advisable to use the Object Browser to instantiate complex classes. Examples of classes that should be avoided include:

• Classes whose properties perform complex operations that require connectivity to external databases, web services, or other external systems.
• Classes that use special configuration, global data, permissions, or require other special facilities in the context of the running application.
• Classes with static constructors that may have undesirable side effects when run in the Object Browser.