mefx - Why can't I see any output from the command ?

Jun 18, 2010 at 3:52 PM

Anyone have any ideas what might be wrong. I'm using NET 4 and the latest mefx that's supposed to work with NET 4.  No matter what I do I don't seem to get any output from any command other than when I just enter the mefx command. I use the /verbose the /parts etc, etc and get nothing at all.  I have mefx running in a DOS command window on a vista machine and running with admin privs.

Directory of C:\Output\Debug

06/18/2010  06:56 PM    <DIR>          .
06/18/2010  06:56 PM    <DIR>          ..
06/18/2010  06:18 PM            24,064 test.dll
05/13/2010  07:15 PM            18,944 mefx.exe
05/13/2010  07:15 PM            30,720 Microsoft.ComponentModel.Composition.Diagnostics.dll
06/18/2010  06:56 PM    <DIR>          Resources
02/21/2010  01:05 PM           238,080 System.ComponentModel.Composition.dll
02/21/2010  01:05 PM           804,352 System.ComponentModel.Composition.pdb
02/21/2010  01:05 PM           318,816 System.ComponentModel.Composition.xml


C:\Output\Debug>mefx /file:BookLibrary.Applications.dll /parts /verbose

<<<<<<<<<<< NOTHING IS OUTPUT WRITTEN HERE >>>>>>>>>>>>>>>>>>>>>>

C:\Output\Debug> mefx
Managed Extensibility Framework Explorer Version 0.4.3555.17540
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

Built for: System.ComponentModel.Composition, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089

Usage:     mefx.exe [assembly files and directories] [action] {options}

Example:   mefx.exe /file:MyAssembly.dll /causes /verbose

Switches:

  /?

      Print usage.

Developer
Jun 18, 2010 at 5:10 PM

Was BookLibrary.Application.dll built against the same version of System.ComponentModel.Composition? If one or the other was built against the codeplex version and the other built against the .Net 4.0 released version then mefx will not be able to see any of the ExportAttributes because they are essentially different types.

 

Jun 18, 2010 at 5:16 PM

1am in the morning here so I'll look into that tomorrow. I had success before but now I started using the libraries in Prism 4 drop. Maybe they are different. In the meantime is there any easy way to look at a .dll and fine out what versions were used in the build? I seem to remember a utility for looking into DLL's but can't remember what it was called.

Thanks,

Developer
Jun 18, 2010 at 11:01 PM

Reflector http://www.red-gate.com/products/reflector/ is an great tool for doing that. 

Jun 19, 2010 at 6:53 AM

Weshaggard you were correct. My dlls were being built with a different version of System.ComponentModel.Composition. I fixed that and I can now see the mefx output.

Thanks for your help