Dependency scanning

[MortSkil]

I added a .NET assembly to a Feature in Files, clicked Scan and loads of dependencies were added, even from the .NET Framework directory.

Why are common .NET features added? Are there recommendations on which to remove, and is it possible to set a filter, so that not only dependencies in one or more source directories are added?

I guess the dependencies referenced from \\Windows\\Assembly\\nativeimages1_v1.1.4322\\<name>\\<ver>_<GUID> should be left out, as these are natively JIT compiled on the development platform.

I think the need for manually deleting detected dependencies is a little annoying.

What happens if applications from different features share dependencies? Is there an easy way to move these dependencies to "Feature independent"?

[MichaelNesmith]

Sorry, the dependency scanner does not support filters right now. You can always review what it finds and remove them manually, at least this is a safe approach.

You can move files to feature independent using the MSIcode view. Just cut the Install Files commands for the files that you want to move out of the feature they belong to (use the code navigation drop-downs for this), and then add them right below [OFFLINE FILES] which is your feature independent section.

[MortSkil]

Is it possible to pass command line arguments when scanning dependencies?

If not - it would be great to have the possibility to do so, because some programs bomb out if they have no arguments

[MichaelNesmith]

This is a good feature suggestion, thank you!