Where is DelegateCommand in 4.2??

Topics: Prism v4 - WPF 4
Mar 10, 2014 at 1:09 PM
I have updated my project with the Prism 4.2 pre-release nuget packages, but I don't seem to have delegate command within them?? Cannot find it to resolve. I know they're in Prism.Mvvm.
Mar 10, 2014 at 3:27 PM
Hi James,

You may find the Delegate Command on the following namespace:
  • Microsoft.Practices.Prism.Commands;
It is indeed on the Prism.MVVM project solution.

I hope this helps,

Gabriel Ostrowsky.
Mar 10, 2014 at 4:11 PM
As far as I know this is not part of the nuget packages though is it?
Mar 10, 2014 at 5:19 PM
Hi James,
I have actually reproduced the issue you mentioned regarding Prism 4.2 Pre-Released nuget package. This package would contain the following assemblies taking into account that it is a beta realease:

  • Microsoft.Practices.Prism.dll
  • Microsoft.Practices.Prism.Interactivity.dll
  • Microsoft.Practices.Prism.SharedInterfaces.dll
You could verify the assemblies available in the Nuget package with the Nuget Package Explorer which you may download it from the following site:

Therefore, you would need to manually add the Prism.MVVM assembly into the corresponding project until it gets added to the Nuget Package.

Gabriel Ostrowsky
Mar 10, 2014 at 5:34 PM
Thanks for your help.

I might just wait until this is released though. Any idea on the progress of the full release?
Mar 11, 2014 at 10:34 AM
I did try this, but I keep getting the following build error when referencing DelegateCommand:

Error 15 The type 'Microsoft.Practices.Prism.IActiveAware' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Practices.Prism.SharedInterfaces, Version=, Culture=neutral, PublicKeyToken=null'. C:\Projects\Columbus\Common\Infrastructure\PagedListCommands.cs 128 67 Common

I'm not even using IActiveAware in the class, and SharedInterfaces is there anyway, all I have done is added the dll to the package as you suggested.
Mar 11, 2014 at 6:19 PM
Hi James,

I wasn't able to reproduced the error you mentioned. However, notice that I suggested you to add the assembly directly into the project, without needing to modify the Nuget package.

If this still does not solve your problem I would appreciate if you could send a small sample that would show the issue, so I can debug it and give you better support on this.

Gabriel Ostrowsky.
May 7, 2014 at 10:39 AM
All sorted in the final release anyway. Thanks for your help.