When creating a new site with the plugin for visual studio this folder is empty but when creating from deployment center and then upgrade the solution it is not. I have tried to remove the files in this folder and it works great for the regular EPiServer Site.
But! I found out that EPiServer CMO 7.5 does not work without having the 7.5 files in that folder so I had to put them back.
Are there any more times these files are needed?
Which "files" are you referring to that have to be in the modulesbin? If you do an install through deployment center and upgrade, you are recommended to move your modules as suggested in this blog post:
Thanks for the link, it explains a lot
The files I need in modulesbin for CMO to work is EPiServer.Packaging.CmdAPI.dll, EPiServer.POackaging.dll, EPiServer.Packaging.UI.dll and NuGet.Core.Dll
For CMO I also need the CMO and LiveMonitor folder to be in the old Modules-folder in the appdata-folder
Both the Framework, CMS and Packaging UI:s are moved from modulesbin to bin in the 7.6 upgrade since they were chaned from being add-ons to regular NUGET-packages.
Do you think I will get any problems having them in the modulesbin so I can get CMO to work?
These files should be located in the regular bin-folder after upgrading to EPiServer 7.6. What issues are you having if you have them there but not in modulesbin?
Ok, I compared now with a Alloy project and in my projects I did not have these files in the bin folder so when looking in the Alloy I noticed that it had two packages that I did not have, Add-on store plattform and Add-on store UI. I will try to add these to my solution and see if those files will be added then
This did solve my problem with CMO, after adding those packages I could remove the files from modulesbin, good to know.