MVVM Light assembly conflict with Microsoft.Practices.ServiceLocation -



MVVM Light assembly conflict with Microsoft.Practices.ServiceLocation -

i've got issue wpf application cannot published clickonce.

the application uses nuget packages mvvm lite 4.1.26.1, unity 2.1.505.2, commonservicelocator 1.0.

the problem when publish, build fine, error when seek , install clickonce package:

unable install or run application. application requires assembly microsoft.practices.servicelocation version 1.0.0.0 installed global assembly cache (gac) first.

i did digging , saw there 2 references assembly in manifest, , 1 of them marked prerequisite can't rid of:

<dependency> <dependentassembly dependencytype="prerequisite" allowdelayedbinding="true"> <assemblyidentity name="microsoft.practices.servicelocation" version="1.0.0.0" publickeytoken="59d6d24383174ac4" language="neutral" processorarchitecture="msil" /> </dependentassembly> </dependency> <dependency> <dependentassembly dependencytype="install" allowdelayedbinding="true" codebase="microsoft.practices.servicelocation.dll" size="29760"> <assemblyidentity name="microsoft.practices.servicelocation" version="1.0.0.0" publickeytoken="31bf3856ad364e35" language="neutral" processorarchitecture="msil" /> <hash> <dsig:transforms> <dsig:transform algorithm="urn:schemas-microsoft-com:hashtransforms.identity" /> </dsig:transforms> <dsig:digestmethod algorithm="http://www.w3.org/2000/09/xmldsig#sha256" /> <dsig:digestvalue>eee+a+dqmhpsy/aplxripxdep8ustazhxhclbu0iwyc=</dsig:digestvalue> </hash> </dependentassembly> </dependency>

i'm pretty sure issue clickonce downwards there beingness 2 references assembly same version (but notice different public key tokens).

i created simple repro follows:

create new wpf application add nuget bundle mvvm lite add nuget bundle unity (also adds dependant bundle called commonservicelocator) build , publish wpf application try , install published myapp.application clickonce package....get error detailed above

here's repro project:

skydrive repro project

any ideas how might on this?

yes. mvvmlight servicelocation assembly uses different public key token every other public implementation. has made life nightmare quite time. had rip out nuget assemblies , go file references in mutual directory now. waiting laurent prepare this.

mvvm-light

Comments

Popular posts from this blog

web services - java.lang.NoClassDefFoundError: Could not initialize class net.sf.cglib.proxy.Enhancer -

Accessing MATLAB's unicode strings from C -

javascript - mongodb won't find my schema method in nested container -