After I skipped this day, I found this:
Open the .proj file in a text editor and look at the very top of the file, there will be a list of sections of the PropertyGroup in XML. Take a look at the first, if it says x86 or nothing but AnyCPU, change it to say AnyCPU and save it.
<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration> <Platform Condition=" '$(Platform)' == '' ">x86</Platform>
it should be:
<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003"> <PropertyGroup> <Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration> <Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
Why? I am not 100% sure, but it seems that Visual Studio does not modify this part of the project file (if so, I donβt know when exactly), since you choose the assembly configuration in the user interface and use it instead. However, since Expression Blend (using version 4) does not allow you to choose the assembly configuration, it simply selects the top one. As a result, you get "Invalid XAML", and all your links have next to them (!).
In my opinion (and knowing my analysis might be wrong), this is a flaw in Expression Blend. Not only can he use any build configuration that the studio can use, you can also choose one.
source share