Although Expression Blend and Visual Studio can work on the same solution / project files, they remain two separate IDEs and it is not uncommon for certain functionality to work correctly in the Visual Studio design-time environment and throw an error in the Expression Blend one. The Blend error output does not always help much with identifying the reason for the erroneous behavior:
This clearly does not give us enough information to track the problem down. Fortunately there is an easier way to detect the problem instead of wandering around the code in a manual “debugging” session – the Visual Studio debugger.
Here is a step-by-step guide that explains how to identify Expression Blend exceptions through the Visual Studio 2008 IDE:
Hope this helps.
Copyright © 2017, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.