ArgumentException: Unable to find a module by assembly 'EPiServer.Forms, Version=5.2.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' (Parameter 'moduleAssembly') about foundation HOT 12 CLOSED

@jon419 Appreciate that!

Going ahead and closing this.

from foundation.

Found the reason but don't know the cause. On the left a working version where the modules/_protected folder contains the actual ZIP on the right there's a whats looks like a Windows symbolic link to the package in Visual Studio. Trying to figure out why this is the case and what can be changed to configure/fix it. If you want to fix it today copy in the packages from your /.nuget/ folder and all works fine

from foundation.

I've seen this behaviour as well (more details - https://blog.tech-fellow.net/2021/09/03/how-to-pack-your-shell-module-for-optimizely-content-cloud/). This is related to how VS installs package and how scripts are executed at that time.

However after build package files were copied correctly (same happens on publish). But here - to launch the project you have to build it ;)

Weird indeed.

Tried dotnet build ?

from foundation.

I can see the modules in the right place in the bin folder but it still complains when starting so thought it was some Dojomojo going on. Still doesn't feel right having an effective symbolic link in VS to a Nuget package in the .nuget cache location though. It's only on a specific (new build) VM I noticed it.

from foundation.

Copying the /.nuget/ folder packages doesn't seem to work for me. Has anyone been able to figure this out yet?

Unable to find a module by assembly 'EPiServer.Forms, Version=5.2.0.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7' (Parameter 'moduleAssembly')

from foundation.

@joshuaonwezen You should not copy that folder, only the missing ZIP file.

P.S. Optimizely should fix the virtual path provider so that it will use sim links. The hack we are doing with modules is not the right approach to using NuGet packages.

from foundation.

I had the same issue. Copied the ZIP file and the app run, but Admin does not work - issues with Forms:

And some weird exception:

Has anyone successfully run the latest version?

from foundation.

I have the same issue which for now is solved my moving the zip file. Would love to get a fix for this.

from foundation.

I'm running into this issue on a mac using .net6 and can't seem to get this working.

Can someone who has created a temporary fix provide more specifics?

I have the zip file in the bin/Debug/net.60/modules/_protected folders for both EPiServer.Forms and EPiServer.Forms.UI. I even see them in finder so I'm not sure where the group is saying to copy them.

And obviously, I'm not sure why the error is happening anyway, as those packages are installed (even did a dotnet install for both).

Any help would be greatly appreciated - relatively urgent POC.

from foundation.

I figured out how to move the files...all good here.

from foundation.

I am no longer seeing this issue when building a new site. Would it be possible for someone else that previously encountered the problem to give it a quick test? Thanks!

from foundation.

@daniel-isaacs - I have confirmed on our end that the latest main branch is working without this error. We had it a couple weeks ago, but we are good now.

from foundation.