Jim U

Thanks Chris. We like to keep our client folder 'nice & clean' so we've been using AssemblyCache as it's easy to delete & re-create. Now we've identified we need it to be in an add-on that's fine. In this case we had a new developer doing a old Sage training course so he was building the .dll without having any add-ons installed.

I think we've found the issue, we had to install an add-on package which included the assembly, else it was removed (maybe)?

Hi, A while ago we started to build/copy our assemblies into Sage\Sage200\AssemblyCache\ (from Visual Studio) for debugging during development but we've noticed recent Sage 200 versions have started to delete some of these files at login/start-up. At first we only noticed this for Sage.Accounting.Datamodel.dll but one of our devs. is now having the same issue with our bespoke .dlls. This happens if we copy the assembly manually or build to the AssemblyCache folder & it also doesn't matter if we open Sage 200 from Visual Studio or just from the desktop icon. Has anyone else had similar issues or can anyone tell me what 'logic' Sage could be using to decide which .dlls to remove? Thanks Jim