You might try updating your Castle.Windsor assembly (and reference). I'm on uCommerce v3.6.1.13149 and have the same version of uCommerce.Infrastucture as you, but my Castle.Windsor is v3.2.0.2401
did you fix this using Kent's solution? Otherwise take a look here:
Looks like you ran into DLL hell. In uCommerce we've refactored all our dependencies into bin/uCommerce/ so that we do not run into conflicts with other apllications in Umbraco. Howver it is not esay to get .NET framework to work as you want it to. For your problem there's a couple of solutions you can try.
In version 3.6.3 there's a hotfix for exactly that problem. If you want to fix it now, there's two solutoins you can use:
In your page where you use Infrastructure you have to explicitly reference your DLL with a register assemblt with fully qualified assembly information
<%@RegisterAssembly=
Another solution is to register the dll in web.config under:
I updated umbraco and ucommerce and manually moved som old dll. that uCommerce left in bin after the update, somehow I got it to work but it was a pain...
Error when using UCommerce.Infrastructure
Compiler Error Message: CS1705: Assembly 'UCommerce.Infrastructure, Version=3.6.1.13149, Culture=neutral, PublicKeyToken=null' uses 'Castle.Windsor, Version=3.2.0.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc' which has a higher version than referenced assembly 'Castle.Windsor, Version=2.5.1.0, Culture=neutral, PublicKeyToken=407dd0808d44fbdc'
What can I do?
You might try updating your Castle.Windsor assembly (and reference). I'm on uCommerce v3.6.1.13149 and have the same version of uCommerce.Infrastucture as you, but my Castle.Windsor is v3.2.0.2401
Hi Kim,
did you fix this using Kent's solution? Otherwise take a look here:
Looks like you ran into DLL hell. In uCommerce we've refactored all our dependencies into bin/uCommerce/ so that we do not run into conflicts with other apllications in Umbraco. Howver it is not esay to get .NET framework to work as you want it to. For your problem there's a couple of solutions you can try.
In version 3.6.3 there's a hotfix for exactly that problem. If you want to fix it now, there's two solutoins you can use:
In your page where you use Infrastructure you have to explicitly reference your DLL with a register assemblt with fully qualified assembly information
Another solution is to register the dll in web.config under:
<compilation defaultLanguage="c#" debug="false" batch="false" targetFramework="4.0">
<assemblies>
Again you have to use the fully qualified name.
Hope this helps.
Regards
Morten
I updated umbraco and ucommerce and manually moved som old dll. that uCommerce left in bin after the update, somehow I got it to work but it was a pain...
Sounds great.
Morten
is working on a reply...