Open orchardbot opened 12 years ago
AimOrchard commented:
I ran into this issue before.
middlewest commented:
Did you resolve the issue?
@Piedone commented:
You could just delete the Dependencies folder.
Related: #2810
I am trying to update a single dll of a module, but the dll file is in use in Dependencies folder. How to do that, without restart the entire site (multitenant in my case)?
You can't update a DLL of an ASP.NET app without restarting it, Orchard or not.
I never tried yet but I have doubts about that @Piedone. If we dynamically compile them and load them why could'nt we dynamically update them ?
@Piedone for other ASP.NET apps I always overwrote dll without problems.
@Piedone created: https://orchard.codeplex.com/workitem/18509
Repro: 1) Take an Orchard 1.3 source installation (already set up). 2) Overwrite the source files with the 1.4 source. 3) Rebuild or even clean the project. 4) Get an exception regarding that there is a mismatch of version of Lucene.NET assemblies.
That's because there remains an outdated dll in the App_Data/Dependencies, even after the solution was cleaned and rebuilt. Solution is to simply delete the folder but this is not obvious.
I think this is not specific to the 1.3-1.4 migration but could happen every time a dependency is updated.