Don't miss out Virtual Happy Hour this Friday (April 26).
Try our conversational search powered by Generative AI!
AI OnAI Off
what nuget packages are needed for getting Find 10 up and running in commerce manager?
Hi,
If you are using FindSearchProvider, you should only install it and let it figures out which packages should be installed.
Otherwise I think you don't have to install Find packages to CM.
Regards,
/Q
Nov 10, 2015 12:04
This is also what we have done, but the EPiServer.Commerce.FindSearchProvider has a dependency on EpiServer.Find.CMS package which pulls in, among other things, EPiServer.Find.UI and EPiServer.Find.Blocks, and these are the two assemblies causing issues. I have to manually delete them to get commerce manager to start.
I had a chat with dev support and a support incident has been created.
Nov 10, 2015 12:08
Exactly what packages are needed on the commerce manager site to get it up and running with Find 10?
We are starting with packages EPiServer.CommerceManager 9.1 and it pulls in EPiServer.Commerce.Core 9.1 which in turn pulls in EPiServer.CMS.Core and related packages.
Now the commerce manager can start and everything seems to work just fine.
Then we try to add EPiServer.Commerce.FindSearchProvider 8.10.0 so we can configure a search provider for commerce which in turn pulls in a lot of packages. Now commerce manager can no longer start:
-----
While loading .NET types from "EPiServer.Find.UI" the following error(s) was reported:
- System.IO.FileNotFoundException: Could not load file or assembly 'EPiServer.Cms.Shell.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' or one of its dependencies. The system cannot find the file specified.
File name: 'EPiServer.Cms.Shell.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7'
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
While loading .NET types from "EPiServer.Find.Blocks" the following error(s) was reported:
- System.IO.FileNotFoundException: Could not load file or assembly 'EPiServer.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' or one of its dependencies. The system cannot find the file specified.
File name: 'EPiServer.UI, Version=9.0.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7'
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].