Paul

The inclusion of files within the folders underneath the inf folder is down to the referencing of those files in Tab Groups (Button Groups) that have changed and are included in the component.

I also look after copying of the dlls my self in components e.g.

CopyFile(GetInstallDir() + "\\inf\\QuickLookDLL2017\\QuickLook.dll", GetInstallDir() + "\\CustomDotNet\\QuickLook.dll")

Ok - but there are no references to the extra dll file in the install script, nor in Custom_Tabs.Tabs_CustomFileName where Tabs_Component = .

Is there somewhere else I should look?

It should only be the entries in the custom_tab metadata table that determines inclusion.

Is this a major problem? You could just remove the offending dll?

It's not a major problem and I have removed the extra dll; however, it's an indication that all is not as it should be and it makes me uncomfortable. As far as I can determine, it shouldn't be exporting the extra dll, but it is so there's something amiss and I want to fix it along with all the other things that we have to fix when a component is scripted.

There must be some other reference that Component Manager uses to decide which dlls to include ...?

Paul

Personally I always manage the copying of DLLs myself. The example below comes from one of the examples in the Downloads section.

CopyFile(GetInstallDir() + "\\inf\\QuickLookDLL2017\\QuickLook.dll", GetInstallDir() + "\\CustomDotNet\\QuickLook.dll")

I let the component manage ASP files but dlls I copy myself.

I have just scripted a different component for a different project, developed on a different CRM installation. This time, the component manager omitted to include the associated dotnet dll, even though there are numerous references to it in the .es file.