Phew! I've been searching for a solution for hours.
uCommerce keeps overwriting these files every time i build:
bin/log4net.dll and bin/Lucene.Net.dll
It seems like it takes the files from the folder bin/ucommerce/ and moves them to bin. But this breaks umbraco. Because the files are not valid versions. What to do?
I have found other threads with this problem, and the workaround is to copy some backup'ed original files back after every build, but that is not a great solution :-/
Latest uCommerce version 6.6.2.15058. Umbraco 7.2.1
UPDATE:
I changed the names of the bin/ucommerce files to uclog4web.dll & ucLucene.Net.dll
If this is happening when you're compiling, I think you're able to find the references in your project and then go to the properties window and tell it not to copy it to the bin folder.
The latest Razor store does not reference log4net.dll nor Lucene.Net.dll. On a succesful build, the Razor store will run the script called DemoStoreDeploy.cmd. In it only very specific assemblies are copied to bin.
So I do not think the razor store is the one causing the copying of assemblies.
Renaming DOT.NET assemblies results in invalid assemblies. So that is not a good idea :-/
uCommerce places log4net.dll and Lucene.Net.dll and other dependencies in the bin/ucommerce folder, precisely to allow you to have other versions of the assemblies in bin.
So please take a look at either your referenced assemblies, or your post build steps, for an explanation..
I have been made aware of a behavior of Visual Studio, that if you add references to assemblies located in bin/ucomerce, it will output them in bin, thereby overwriting the very assemblies we are trying to protect.
Also, renaming the assembly does not result in an invalid assembly. I stand corrected! :-) You just need to use the codebase reference at runtime.
Are there any particular reason you need to reference assemblies from bin/ucommerce in your visual studio project?
I've had the same problem my solution was to have a folder containing all the correct assemblies and using VS postbuild event to copy them into the bin folder making sure i hvae everything i need.
Unfortunately i have to update the folder when updating umbraco and ucommerce, but it is working pretty well for me.
uCommerce overwrites bin/ log4net & Lucene. Breaking Umbraco
Hi
Phew! I've been searching for a solution for hours.
uCommerce keeps overwriting these files every time i build:
bin/log4net.dll and bin/Lucene.Net.dll
It seems like it takes the files from the folder bin/ucommerce/ and moves them to bin. But this breaks umbraco. Because the files are not valid versions. What to do?
I have found other threads with this problem, and the workaround is to copy some backup'ed original files back after every build, but that is not a great solution :-/
Latest uCommerce version 6.6.2.15058. Umbraco 7.2.1
UPDATE:
I changed the names of the bin/ucommerce files to uclog4web.dll & ucLucene.Net.dll
Updated the web.cofig:
<dependentAssembly>
<assemblyIdentity name="Lucene.Net" publicKeyToken="85089178b9ac3181" />
<codeBase version="3.0.3.0" href="bin\ucommerce\ucLucene.Net.dll" />
dependentAssembly>
Hi Henrik,
If this is happening when you're compiling, I think you're able to find the references in your project and then go to the properties window and tell it not to copy it to the bin folder.
Best regards
Martin
Hello Henrik,
What version of the Razor store are you using?
The latest Razor store does not reference log4net.dll nor Lucene.Net.dll.
On a succesful build, the Razor store will run the script called DemoStoreDeploy.cmd. In it only very specific assemblies are copied to bin.
So I do not think the razor store is the one causing the copying of assemblies.
Renaming DOT.NET assemblies results in invalid assemblies. So that is not a good idea :-/
uCommerce places log4net.dll and Lucene.Net.dll and other dependencies in the bin/ucommerce folder, precisely to allow you to have other versions of the assemblies in bin.
So please take a look at either your referenced assemblies, or your post build steps, for an explanation..
Kind regards,
Jesper
Hello Henrik,
I have been made aware of a behavior of Visual Studio, that if you add references to assemblies located in bin/ucomerce, it will output them in bin, thereby overwriting the very assemblies we are trying to protect.
Also, renaming the assembly does not result in an invalid assembly. I stand corrected! :-) You just need to use the codebase reference at runtime.
Are there any particular reason you need to reference assemblies from bin/ucommerce in your visual studio project?
Kind regards,
Jesper
I've had the same problem my solution was to have a folder containing all the correct assemblies and using VS postbuild event to copy them into the bin folder making sure i hvae everything i need.
Unfortunately i have to update the folder when updating umbraco and ucommerce, but it is working pretty well for me.
is working on a reply...