Why the hell this fucking little thing doesn't work in VS 2012 ???

        xmlns:cmd="clr-namespace:GalaSoft.MvvmLight.Command;assembly=GalaSoft.MvvmLight.WPF4"


        xmlns:cmd="clr-namespace:GalaSoft.MvvmLight.Command;assembly=GalaSoft.MvvmLight.Extras.WPF4"


        xmlns:cmd=?????????????????????????????????????????????????????????????????????????"

Assuming that you work with WPF4 indeed, it should be

xmlns:cmd="clr-namespace:GalaSoft.MvvmLight.Command;assembly=GalaSoft.MvvmLight.WPF4"

What happens when you try that?

Laurent

Sorry for my first post, I was upset...

I'm using .NET 4.5, with the MVVM Light 4.5 WPF project template, so I assume the good assemblies are referenced.

When I try to use EventToCommand in this XAML: 

<Rectangle Fill="BlueViolet"
                 Width="{Binding Width}"
                 Height="{Binding Height}">
<i:Interaction.Triggers>
    <i:EventTrigger EventName="MouseDown">
    </i:EventTrigger>
</i:Interaction.Triggers>
</Rectangle>

I lost the intelisence and when I try to put cmd:EventToCommand tag VS tell me that: 

`Error 1 The name "EventToCommand" does not exist in the namespace "clr-namespace:GalaSoft.MvvmLight.Command;assembly=GalaSoft.MvvmLight.WPF4".`

Thanks for your answer.

Hi,

No worries.

For WPF 4.5, you need to use the correct assembly name GalaSoft.MvvmLight.WPF45 and not GalaSoft.MvvmLight.WPF4.

Side note: There is a reason why I am using the WPF45 in the assembly name, but I am reconsidering it and it is very possible that I will remove that from a future version of MVVM Light.

Let me know if it still doesn't work with the correction.

Thanks
Laurent 

BTW in VS12, you can type simply xmlns:cmd= and then VS12 should open an Intellisense window proposing the correct namespaces to you.

Cheers

Laurent

I already tried with 45, but it didn''t worked at all (VS send an error).

In the intellisense pop up there's only the 4 version ("clr-namespace:GalaSoft.MvvmLight.Command;assembly=GalaSoft.MvvmLight.WPF4").

Hi,

It sounds like you are using the WPF 4 DLLs with a WPF 4.5 project. Can you send me the project and I'll take a look.

Cheers
Laurent

Even when I create a new MVVM Light WPF 45 project, it adds dlls for .NET 4: 

http://img4.hostingpics.net/pics/324142Capture.png

Seems that you are absolutely right. The project template is faulty. You are the first to report this issue, sorry for that.

I will fix it ASAP. In the meantime, please download the following Zip file:

http://sdrv.ms/UUyOfU

Then right click on the zip file and select Properties. Click on the Unblock button. Then extract the file.

In your project, remove the WPF 4 references and replace with the WPF 4.5 references. In the XAML, use WPF45 instead of WPF4.

Sorry for the inconvenience, but thanks for reporting the issue. 

Cheers
Laurent 

Thanks for your answers.

I have been struggling with EventToCommand and MouseMove.  I have tried binding to my ViewModel and to my View, but nothing fires.  Please help..

I am working with Silverlight 4, NOT WPF.  I think I saw somewhere that EventToCommand does not work with Silverlight except for the Load event.  Bbut for the life of me I can not find that post again.

I have pasted my code and XAML below for your review.  Thanks!

    Public Shared ReadOnly MouseMoveCommandProperty As DependencyProperty = DependencyProperty.Register("MouseMoveCommand", GetType(RelayCommand(Of MouseEventArgs)), GetType(MyViewModel), Nothing)
    Public Property MouseMoveCommand As RelayCommand(Of MouseEventArgs)
        Get
            If GetValue(MouseMoveCommandProperty) Is Nothing Then
                Return New RelayCommand(Of MouseEventArgs)(Sub(e) MyMouseMove(e))
            Else
                Return DirectCast(GetValue(MouseMoveCommandProperty), RelayCommand(Of MouseEventArgs))
            End If
        End Get
        Set(ByVal value As RelayCommand(Of MouseEventArgs))
            Me.SetValue(MouseMoveCommandProperty, value)
            RaiseEvent PropertyChanged(Me, New PropertyChangedEventArgs(MethodBase.GetCurrentMethod().Name.Substring(4)))
        End Set
    End Property

    Public Sub MyMouseMove(e As MouseEventArgs)
        Dim p As Point = e.GetPosition(e.OriginalSource)
    End Sub

<Canvas x:Name="MyCanvas" Cursor="{Binding ActionType, Source={StaticResource MyVM}, Mode=OneWay, Converter={StaticResource ActionToCursor}}" 
                    MouseLeftButtonDown="Canvas_MouseLeftButtonDown" 
                    MouseLeftButtonUp="Canvas_MouseLeftButtonUp">

                <i:Interaction.Triggers>
                    <i:EventTrigger>
                        <cmd:EventToCommand Command="{Binding MouseMoveCommand, Source={StaticResource MyVM}}" PassEventArgsToCommand="True"/>
                    </i:EventTrigger>
                </i:Interaction.Triggers>
</Canvas>

For what it is worth...  This works fine:

        Public _initializeSystemCommand As ICommand = New SystemEx.Commands.DelegateCommand(AddressOf InitializeSystem, AddressOf CanExecute)
        Public Property InitializeSystemCommand() As ICommand
            Get
                Return _initializeSystemCommand
            End Get
            Set(ByVal value As ICommand)
                _initializeSystemCommand = value
            End Set
        End Property

        Private Sub InitializeSystem(parameter As Object)
            'Do something interesting
        End Sub

<Canvas Height="768" Width="1024" Background="LightGray" Cursor="Arrow" DataContext="DrawingVM" >
        <i:Interaction.Triggers>
            <i:EventTrigger EventName="Loaded">
                <i:InvokeCommandAction Command="{Binding InitializeSystemCommand, Source={StaticResource DrawingVM}, Mode=TwoWay}" CommandParameter="L" />
            </i:EventTrigger>

</Canvas

Here is a cut and paste out of your on Drag&Drop with EventToComand....  However, I can confirm that the code does NOT execute or I would receive notification of the mouse move through Messaging which notifies other elements of the event.

An issue with Visual Studio 2010

In the course of preparing this article, I noticed an issue in Visual Studio 2010 when I attempt to debug the HandleDropCommand implementation. Even with a breakpoint placed within the code, the debugger does not break. I am not sure right now what is the reason, and the code does get executed, but this complicates debugging of course. I am investigating and talking to Microsoft about that, but right now I am not sure where it comes from.