Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Delete EPiServer.Commerce.Shell folder under modules/protected then try reinstalling.
Also check references. In your web project goto dependencies/packages. Make sure they all look loaded.
Hi,
Just to add if you have a multi-project setup, ensure that you have consolidated the nuget packages.
I do remember on a recent upgrade while the main project was referencing the correct version a warning appearing informing me it was using a different version.
Might be worth checking the version of the dll's in the bin folder also.
Paul
I am setting up .Net6 Optimizely solution, reusing existing code from .net47.
I can see login/register page, but after login I got such error as below.
- I had EPiServer.Commerce v14.11.0 nuget referenced,
- I put all EPi nugets references in single core project
- EPiServer.Commerce.Shell.dll gets added to modules/_protected directory with correct version
- EPiServer.Commerce.Shell.dll is present in bin/Debug/net6.0 folder with correct version
- cleaned bin/obj folders in all solution projects before build
I go through bunch of topics on and off this forum and can't fix it :/
Here are some troubleshooting steps that you can check.
* Check that the correct version of 'EPiServer.Commerce.Shell.dll' is referenced and located in the appropriate folder.
* Ensure all necessary assembly references are correctly added to the project.
* Clean the solution, rebuild it, and make sure the DLL is included in the build output.
* Verify file permissions for the DLL and ensure the application has access to it.
* Double-check the file location and consider re-adding the reference or copying the DLL to the correct location.
* Review any custom assembly loading logic or potential conflicts with other assemblies.
If these steps don't resolve the issue, consult the documentation or seek support from EPiServer for assistance.