3

Resolved

VS 2012 XML Design time error

description

When using this with VS 2012 I get this design time error: "The type 'EventToCommand' from assembly 'GalaSoft.MvvmLight.Extras.SL5' is built with an older version of the Blend SDK, and is not supported in a Silverlight 5 project." I installed the 4.0.23.4 package, but My assemblies are still versioned 4.0.23.35578....did I miss something?
by thomasfj on Today at 11:46

comments

lbugnion wrote Oct 24, 2012 at 10:20 AM

Hi,

This is correct, Microsoft released a new version of System.Windows.Interactivity and because it is strongly signed, every depending assembly needs to be rebuilt. I am working on it, will publish a fix in a few days.

Sorry for the inconvenience
Laurent

onovotny wrote Nov 11, 2012 at 3:06 PM

This issue is not present in the PCL version as it already uses the newest interactivity package.

https://nuget.org/packages/Portable.MvvmLightLibs

lbugnion wrote Nov 11, 2012 at 9:53 PM

Actually this is solved in V4.1. Download from http://mvvmlight.codeplex.com/releases/view/96993. I will make the DLLs available on Nuget next week.

adhemar82 wrote Nov 13, 2012 at 9:07 PM

I'm using version MVVM Light 4.1.23.0 (via NuGet) and I'm still seeing this error on Visual Studio 2012 in a WPF project. Should this be resolved?

The event to command binding works fine at runtime, by the way. Just the designer is complaining.

VincMan wrote Dec 5, 2012 at 7:33 AM

Hi,
I'm still having this issue too. V.4.1.23.0 (downloaded here yesterday), VS2012, WPF project, runtime fine, designer not.

"The type 'EventToCommand' from assembly 'GalaSoft.MvvmLight.Extras.WPF45' is built with an older version of the Blend SDK, and is not supported in a Windows Presentation Framework 4 project."

DarkPrisma wrote Mar 5 at 8:39 AM

I have the same issue in 4.1.27.22784

VincMan wrote Mar 8 at 8:01 PM

It now works after I have installed the "Visual Studio 2012 Update 2 CTP". See http://www.microsoft.com/en-us/download/details.aspx?id=36833

metacircle wrote Mar 12 at 4:04 PM

Hi Laurent,

this is still happening with VS2012 and the latest MVVM Light NuGet package (4.1.27.22692)

lbugnion wrote Mar 12 at 5:50 PM

Hi,

It works fine now but you need the Update 2 of Visual Studio 2012. The error is due to a bug in Visual Studio and Update 2 fixes it.

Cheers
Laurent

metacircle wrote Mar 17 at 12:55 PM

Thank you for the information. I will have to wait until my company rolls out this update then. At home it is working fine now.

Sign in to add a comment or to set email notifications